Last Call: <draft-ietf-l3vpn-mvpn-infra-addrs-04.txt> (IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPN) to Proposed Standard

The IESG <> Tue, 31 May 2011 13:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D44C9E081F; Tue, 31 May 2011 06:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uaz6WbLzmXWk; Tue, 31 May 2011 06:29:30 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id 60F63E0729; Tue, 31 May 2011 06:29:30 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-l3vpn-mvpn-infra-addrs-04.txt> (IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPN) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 3.55
Message-ID: <>
Date: Tue, 31 May 2011 06:29:30 -0700
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 31 May 2011 13:29:34 -0000

The IESG has received a request from the Layer 3 Virtual Private Networks
WG (l3vpn) to consider the following document:
- 'IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast
  <draft-ietf-l3vpn-mvpn-infra-addrs-04.txt> as a 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 mailing lists by 2011-06-14. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


To provide Multicast VPN (MVPN) service, Provider Edge routers
originate BGP Update messages that carry Multicast-VPN ("MCAST-VPN")
BGP routes; they also originate unicast VPN routes that carry MVPN-
specific attributes.  These routes encode addresses from the
customer's address space, as well as addresses from the provider's
address space.  These two address spaces are independent, and the
address family (IPv4 or IPv6) of the two spaces may or may not be the
same.  These routes always contain an "address family" field that
specifies whether the customer addresses are IPv4 addresses or
whether they are IPv6 addresses.  However, there is no field that
explicitly specifies the address family of the provider addresses.
To ensure interoperability, this document specifies that provider
IPv4 addresses are always encoded in these update messages as four-
octet addresses, and that the distinction between IPv4 and IPv6 is
signaled solely by the length of the address field.  Specific cases
are explained in detail.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.