Hello Li,

Thanks for the review. Responses inline.....

                              Ron


________________________________
From: zhangli (CE) <[email protected]>
Sent: Friday, August 21, 2026 4:09 AM
To: Christian Hopps <[email protected]>; [email protected] <[email protected]>
Cc: [email protected] <[email protected]>; [email protected] 
<[email protected]>; [email protected] 
<[email protected]>
Subject: RE: [Lsr] WG adoption call for draft-many-lsr-power-group-03 (Ends 
2026-08-30)

Hi All,

I have reviewed this draft and have a few comments. Please let me know if I 
have misunderstood anything.

1. General comment: This draft introduces several new TLVs/sub-TLVs but does 
not clearly explain their necessity or usage. If this information is already 
covered in draft-many-teas-power-steering, please add a reference to that 
draft. Otherwise, it would be helpful to provide more context to make it easier 
for readers to understand. For example, why is the Unidirectional Sleeping 
Bandwidth Sub-TLV needed, and how should it be used?

[rb] Please see draft-many-teas-power-steering, Section 6.

2. Interface PSP Sub-TLV: The definition of the Interface PSP sub-TLV is 
somewhat confusing. Section 2.1 defines PSP as "Power Saving Potential," this 
concept is abstract. From the discussion on the mailing list, I understand it 
is the power that may be saved if a power group goes to sleep. It is 
recommended to provide more clarification on this point.

[rb] Please see draft-many-teas-power-steering, Section 3 and Section 6.3.


3. Unidirectional Sleeping Bandwidth Sub-TLV: The definition of sleeping 
bandwidth in this draft is not aligned with draft-many-teas-power-steering.
In this draft, it is defined as: "the maximum bandwidth [RFC5305] minus the 
bandwidth currently allocated to RSVP-TE label switched paths that was 
transitioned to power-sleep."
While in draft-many-teas-power-steering, it is defined as: "this value 
represents the sleeping bandwidth on a link."
It is recommended to align these definitions to avoid confusion.

[rb] Good catch. I will fix this to align with the 
draft-many-teas-power-steering


I hope these comments can be addressed before the draft is adopted.

Best regards
Li

-----邮件原件-----
发件人: Christian Hopps via Datatracker <[email protected]>
发送时间: 2026年8月17日 8:57
收件人: [email protected]
抄送: [email protected]; [email protected]; [email protected]
主题: [Lsr] WG adoption call for draft-many-lsr-power-group-03 (Ends 2026-08-30)

Hi Folks,

This begins a 2 week WG Adoption Call for the following draft:

  
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-many-lsr-power-group/__;!!NpxR!g0n9IEp4Z5EWJR38fpoyS5T9s-SbPrKZnCvnWIh2mlrMYP6S8fgWrzaaBxTkP0gdEmfkLXBYm-jtQseIVmFG$

Please indicate your support or objections by August 30th, 2026.

An IPR declaration has been made

  
https://urldefense.com/v3/__https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-many-lsr-power-group__;!!NpxR!g0n9IEp4Z5EWJR38fpoyS5T9s-SbPrKZnCvnWIh2mlrMYP6S8fgWrzaaBxTkP0gdEmfkLXBYm-jtQkmKKmlx$

Authors, please respond to the list indicating whether you are aware of any 
other IPR that applies to this draft.

Thanks,
Chris.

[Call for adoption end date (2026-08-30)]

_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to