Authors -

Thanx for yet another quick update, but the changes to Table 2 are incomplete.
You updated the TLVs for Unidirectional Sleeping Bandwidth, but not for the 
other two sub-TLVs.

    Les

>-----Original Message-----
>From: [email protected] <[email protected]>
>Sent: Friday, October 30, 2026 8:51 AM
>To: [email protected]
>Cc: [email protected]
>Subject: [Lsr] I-D Action: draft-ietf-lsr-pcpps-02.txt
>
>Internet-Draft draft-ietf-lsr-pcpps-02.txt is now available. It is a work item
>of the Link State Routing (LSR) WG of the IETF.
>
>   Title:   IS-IS Support For The Power Conserving Path Placement Strategy
>(PCPPS)
>   Authors: Colby Barth
>            Tony Li
>            Vishnu Pavan Beeram
>            Ron Bonica
>   Name:    draft-ietf-lsr-pcpps-02.txt
>   Pages:   12
>   Dates:   2026-10-30
>
>Abstract:
>
>   [I-D.many-teas-power-steering] introduces a Power Conserving Path
>   Placement Strategy (PCPPS).  When possible, PCPPS concentrates
>   traffic onto a small set of network resources.  When traffic is
>   concentrated onto a small set of network resources, other network
>   resources become idle and can be powered down until they are needed
>   again.  This conserves energy and reduces environmental impact.
>
>   PCPPS uses information that is distributed by an IGP.  This document
>   specifies the IS-IS encoding for that information.
>
>The IETF datatracker status page for this Internet-Draft is:
>https://datatracker.ietf.org/doc/draft-ietf-lsr-pcpps/
>
>There is also an HTML version available at:
>https://www.ietf.org/archive/id/draft-ietf-lsr-pcpps-02.html
>
>A diff from the previous version is available at:
>https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-pcpps-02
>
>Internet-Drafts are also available by rsync at:
>rsync.ietf.org::internet-drafts
>
>
>_______________________________________________
>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