Hi all.
Just a few minor comments:
- The I-D refers to the "EXP" field several times (pages 11, 13, 15,
17...) whereas it is now named "Traffic Class", as per RFC 5462.
- Section 5.8 tackles PCE, thus putting some requirements on the PCE WG:
do we expect that they are endorsed tacitly? In this specific case, it
is only specified as "SHOULD", so impact is limited, but what is the
status of this kind of draft defining requirements over multiple WGs? In
case it be superset by draft-ietf-pce-vpn-req, a reference would be
welcome.
Thanks,
Julien
-----Original Message-----
From: ietf-announce-bounces(_at_)ietf(_dot_)org
[mailto:ietf-announce-bounces(_at_)ietf(_dot_)org] On Behalf Of The IESG
The IESG has received a request from the Layer 3 Virtual Private
Networks
WG (l3vpn) to consider the following document:
- 'Requirements for supporting Customer RSVP and RSVP-TE over a BGP/MPLS
IP-VPN '
<draft-ietf-l3vpn-e2e-rsvp-te-reqts-04.txt> as an Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2009-10-20. Exceptionally,
comments may be sent to iesg(_at_)ietf(_dot_)org instead. In either case,
please
retain the beginning of the Subject line to allow automated sorting.
The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-e2e-rsvp-te-reqts-0
4.txt
IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=
17192&rfc_flag=0
_______________________________________________
IETF-Announce mailing list
IETF-Announce(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf