[BGPCEP-178] Processing of M flag is not correct for SR-ERO subobject Created: 23/Dec/14 Updated: 03/Mar/19 Resolved: 23/Jan/15 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | PCEP |
| Affects Version/s: | Bugzilla Migration |
| Fix Version/s: | Bugzilla Migration |
| Type: | Bug | ||
| Reporter: | Bin Pan | Assignee: | Milos Fabian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2534 |
| Description |
|
As per the PCEP drafts(https://tools.ietf.org/html/draft-sivabalan-pce-segment-routing-03#page-9), SID value represents an MPLS label stack entry as specified as RFC5462. M: When this bit is set, the SID value represents an MPLS label This means MPLS label stack entry has the following 32 bit format where first 20 bits are the label and other 12 bits are the TC, S and TTL values. 0 1 2 3
Label: Label Value, 20 bits But the code(SrEroSubobjectParser.java) does not process the M flag correctly. I correct it as following, please review. } public Subobject parseSubobject(ByteBuf buffer, boolean loose) throws PCEPDeserializerException { } |
| Comments |
| Comment by Dana Kutenicsova [ 19/Jan/15 ] |
| Comment by Dana Kutenicsova [ 19/Jan/15 ] |
|
Resolved for stable/helium |
| Comment by Milos Fabian [ 21/Jan/15 ] |
|
incorporated in draft-update patch for Lithium |