The MPLS WG Archive

[Huub van Helvoort <hhelvoort@chello.nl>]

Hello Steward,

You replied:

>> I checked the appendix II twice (because my left eye is still 10%),
>> I could not find any text referring to setting the S bit.
>> I only see that the 4 octet sequence number is placed right
>> after the shim header.
> 
> The implication of the text is that you can have a packet of the
> form:
> 
> LSE (RFC3032)
> Sequence number
> LSE (RFC3032)
> Payload
> 
> Is that correct?

This is also what I read, and apparently Neil does as well.

> If so what is the setting of the S bit (See RFC3032) in each
> case?

Because the text does not mention any altering of the S-bit
I assume they do not change.

I agree with Neil (see his 2002 post) that this requires a
very carefull configuartion of the network. Checking that
both ends support this feature and closely guard the connectivity
for both diverse routes.

Note that this text is in an appendix, so it does not form
an integral part of the recommendation, i.e. it is not mandatory.

Regards, Huub.

-- 
================================================================
                   http://www.van-helvoort.eu/
================================================================
Always remember that you are unique...just like everyone else...

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls