This document contains a worked example using IP addresses from the 10/8 and 192.168/16 Private Use spaces. It would be far better if the document used addresses from the three documentation/test spaces 192.0.2/24 198.51.100/24 and 203.0.113/24 Unless you can provide a strong reason not to make this change (which looks to me like it would be a simple matter), please do so in a new revision after IETF last call. Thanks, Adrian > -----Original Message----- > From: IETF-Announce [mailto:ietf-announce-bounces@xxxxxxxx] On Behalf Of The > IESG > Sent: 24 November 2014 15:57 > To: IETF-Announce > Cc: bess@xxxxxxxx > Subject: Last Call: <draft-ietf-l3vpn-end-system-04.txt> (BGP-signaled end- > system IP/VPNs.) to Proposed Standard > > > The IESG has received a request from the BGP Enabled Services WG (bess) > to consider the following document: > - 'BGP-signaled end-system IP/VPNs.' > <draft-ietf-l3vpn-end-system-04.txt> as Proposed Standard > > 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@xxxxxxxx mailing lists by 2014-12-08. Exceptionally, comments may be > sent to iesg@xxxxxxxx instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > This document contains a normative Downref to RFC 1027 > > Abstract > > This document describes a solution in which the control plane > protocol specified in BGP/MPLS IP VPNs is used to provide a Virtual > Network service to end-systems. These end-systems may be used to > provide network services or may directly host end-to-end > applications. > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-ietf-l3vpn-end-system/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-ietf-l3vpn-end-system/ballot/ > > > No IPR declarations have been submitted directly on this I-D.