Hi Alexey,


Thanks for your comments. Please see in-line for my response to each of your 
comments. Please let me know if you would have further comments.



Thanks & best regards,

Young



-----Original Message-----

From: Alexey Melnikov [mailto:[email protected]]

Sent: Tuesday, February 5, 2019 6:46 AM

To: The IESG <[email protected]>

Cc: [email protected]; Daniele Ceccarelli 
<[email protected]>; [email protected]; 
[email protected]; [email protected]

Subject: Alexey Melnikov's No Objection on draft-ietf-pce-wson-rwa-ext-11: 
(with COMMENT)



Alexey Melnikov has entered the following ballot position for

draft-ietf-pce-wson-rwa-ext-11: No Objection



When responding, please keep the subject line intact and reply to all email 
addresses included in the To and CC lines. (Feel free to cut this introductory 
paragraph, however.)





Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html

for more information about IESG DISCUSS and COMMENT positions.





The document, along with other ballot positions, can be found here:

https://datatracker.ietf.org/doc/draft-ietf-pce-wson-rwa-ext/







----------------------------------------------------------------------

COMMENT:

----------------------------------------------------------------------



Benjamin's DISCUSS is a superset of issues I spotted, so I am agreeing with it.



In Section 4.1:



     . Wavelength Selection TLV (32 bits): See Section 4.2 for

        details.



Is TLV value 32 bit or the whole TLV? (This is the same issue as raised by 
Benjamin)



YL>> The whole TLV.



In Section 4.3:



   o  Link Identifiers: Identifies each link ID for which restriction

   is applied. The length is dependent on the link format and the Count

   field.



Is the type field extensible?



YL>> Yes.



   See Section 4.3.1. for Link Identifier encoding and Section

   4.3.2. for the Wavelength Restriction Field encoding, respectively.



8.5. New PCEP TLV: Optical Interface Class List TLV



   As described in Section 4.3, a new PCEP TLV is defined to indicate

   the optical interface class list. IANA is to allocate this new TLV

   from the "PCEP TLV Type Indicators" subregistry

   (http://www.iana.org/assignments/pcep/pcep.xhtml#pcep-tlv-type-

   indicators).



   Value             Description                Reference

   ---------------------------------------------------------

   TBD5              Optical Interface          [This.I-D]

                     Class List



I don't see TBD5 referenced anywhere else in the document.



YL>> Thanks for finding this out. Added TBD5 in Section 4.4 where “The encoding 
for the Optical Interface Class List (TBD5) is described …



8.6. New PCEP TLV: Client Signal TLV



   As described in Section 4.3, a new PCEP TLV is defined to indicate

   the client signal information. IANA is to allocate this new TLV from

   the "PCEP TLV Type Indicators" subregistry

   (http://www.iana.org/assignments/pcep/pcep.xhtml#pcep-tlv-type-

   indicators).



   Value             Description                Reference

   ---------------------------------------------------------

   TBD6              Client Signal Information  [This.I-D]



I don't see TBD6 referenced anywhere else in the document either.



YL>> Thanks for finding this out. Added TBD6 in Section 4.4 where “The encoding 
for the Client Signal information  (TBD6) is described …


_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce

Reply via email to