Re: [Pce] WG Last Call for draft-ietf-pce-binding-label-sid-07 (and Code Point Allocation)

["Chengli (Cheng Li)" <[e-mail]>]

Hi Tom, 

Sorry for sending the error diff.

The latest diff is here https://tools.ietf.org/rfcdiff?url1=https://www.ietf.org/archive/id/draft-ietf-pce-binding-label-sid-07.txt&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-binding-label-sid-08.txt

Also, Julien has replied to Adrian about the IANA allocation comments. 
The IANA early allocation will be issued without error type at this time.

Thanks,
Cheng



-----Original Message-----
From: Pce [mailto:[e-mail]] On Behalf Of tom petch
Sent: Monday, March 22, 2021 8:14 PM
To: [e-mail]; [e-mail]
Cc: [e-mail]
Subject: Re: [Pce] WG Last Call for draft-ietf-pce-binding-label-sid-07 (and Code Point Allocation)

Separate to my other comments
________________________________________
From: Pce <[e-mail]> on behalf of [e-mail] <[e-mail]>
Sent: 18 March 2021 11:08

Hi all,

This message initiates a 2-week PCE WG Last Call for draft-ietf-pce-binding-label-sid-07. Please review and share your feedback, whatever it is, using the PCE mailing list. This WGLC will end on Thursday April 1st (no kidding).

Moreover, we have received a request from the authors for a code point allocation to support interoperability testing.

RFC 7120 requires to meet the following criteria to proceed:

b. The format, semantics, processing, and other rules related to handling the protocol entities defined by the code points (henceforth called "specifications") must be adequately described in an Internet-Draft.
c. The specifications of these code points must be stable; i.e., if there is a change, implementations based on the earlier and later specifications must be seamlessly interoperable.

If anyone believes that the draft does not meet these criteria, or believes that early allocation is not appropriate for any other reason, please send an email to the PCE mailing list explaining why. If the chairs hear no objections by Thursday, March 25th, we will kick off the "early" allocation request.

<tp>
I am unclear how much is being requested of IANA here but ..

s.11.1.1 starts the registry at zero which is consistent with the rest of the I-D.  Is there any need to reserve the value of zero as something special?  Probably not but something to consider

TBD4 and TBD5 have almost identical Error-value which I think unhelpful.  The wording should be more distinctive IMHO.  If this is part of the Early Allocation request, then it is better to fix it now rather than getting into IANA in this form. Perhaps 'Unable to amend the..
'Unable to allocate a..
And along with TBD2  and TBD6, as in my separate e-mail, I find 'Binding label/SID' clumsy and would prefer a replacement such as 'Binding value'

Tom Petch




Thanks,

Dhruv & Julien


_________________________________________________________________________________________________________________________

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.

_______________________________________________
Pce mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/pce

_______________________________________________
Pce mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/pce