Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming

["Pablo Camarillo (pcamaril)" <[e-mail]>]

Hi Bruno,

This paragraph is in the context of BGP-LS advertisement for SRv6 capabilities. The text in there is an example of a potential advertised capability.
The detailed definition of how capabilities are advertised belongs to draft-ietf-idr-bgpls-srv6-ext. In my opinion it should be the BGPLS draft the one detailing it.

Thanks,
Pablo.

From: "[e-mail]" <[e-mail]>
Date: Tuesday, 10 December 2019 at 18:37
To: draft-ietf-spring-srv6-network-programming <[e-mail]>
Cc: 'SPRING WG List' <[e-mail]>
Subject: RE: WGLC - draft-ietf-spring-srv6-network-programming
Resent from: <[e-mail]>
Resent to: <[e-mail]>, <[e-mail]>, <[e-mail]>, <[e-mail]>, <[e-mail]>, <[e-mail]>
Resent date: Tuesday, 10 December 2019 at 18:37

[-6man as I believe this is spring specific]

Hi Pablo, authors,


« The
   T.Encaps behavior would describe the capability of node N to perform
   a T.Encaps behavior, specifically it would describe how many SIDs
   could be inserted by N without significant performance degradation.”


Could you please explicit what is meant by ‘how many SIDs’? Especially for .Red.
Is this the number of SID in the SRH?
Because for .Red, the number of SID in the SRH is N-1, with N been the number of SIDs. (as the first SID is not included in the SRH).

Any option works for me. I’m just asking for the behavior to be clear and interoperable.

Thank you,
--Bruno


From: ipv6 [mailto:[e-mail]] On Behalf Of [e-mail]
Sent: Thursday, December 5, 2019 6:15 PM
To: 'SPRING WG List'
Cc: [e-mail]; draft-ietf-spring-srv6-network-programming
Subject: WGLC - draft-ietf-spring-srv6-network-programming


Hello SPRING,



This email starts a two weeks Working Group Last Call on draft-ietf-spring-srv6-network-programming [1].



Please read this document if you haven't read the most recent version, and send your comments to the SPRING WG list, no later than December 20.



You may copy the 6MAN WG for IPv6 related comment, but consider not duplicating emails on the 6MAN mailing list for the comments which are only spring specifics.



If you are raising a point which you expect will be specifically debated on the mailing list, consider using a specific email/thread for this point.

This may help avoiding that the thread become specific to this point and that other points get forgotten (or that the thread get converted into parallel independent discussions)



Thank you,

Bruno



[1] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-05




_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.