< draft-ietf-ion-vpn-id-01.txt		draft-ietf-ion-vpn-id-02.txt >
	Internet Engineering Task Force Barbara A. Fox		Internet Engineering Task Force Barbara A. Fox
	INTERNET-DRAFT Lucent Technologies		INTERNET-DRAFT Lucent Technologies
	<draft-ietf-ion-vpn-id-01.txt> Bryan Gleeson		<draft-ietf-ion-vpn-id-02.txt> Bryan Gleeson
	Expires December 1999 Shasta Networks, Inc.		Expires January 2000 Shasta Networks, Inc.
	Virtual Private Networks Identifier		Virtual Private Networks Identifier
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026.		all provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 3, line 21 ¶		skipping to change at page 3, line 21 ¶
	- In a MIB to configure attributes to a VPN, or to assign a physical		- In a MIB to configure attributes to a VPN, or to assign a physical
	or logical access interface to a particular VPN.		or logical access interface to a particular VPN.
	- In a control or data packet, to identify the "scope" of a private		- In a control or data packet, to identify the "scope" of a private
	IP address and the VPN to which the data belongs.		IP address and the VPN to which the data belongs.
	It is necessary to be able to identify the VPN with which a data		It is necessary to be able to identify the VPN with which a data
	packet is associated. The VPN-ID may be used to make this		packet is associated. The VPN-ID may be used to make this
	association, either explicitly (e.g. through inclusion of the VPN-ID		association, either explicitly (e.g. through inclusion of the VPN-ID
	in an encapsulation header [2]) or implicitly (e.g. through inclusion		in an encapsulation header [2]) or implicitly (e.g. through inclusion
	of the VPN-ID in a signalling exchange [3]).		of the VPN-ID in a ATM signalling exchange [3]). The appropriateness
			of using the VPN-ID in other contexts needs to be carefully
			evaluated.
	There is another very important function that may be served by the		There is another very important function that may be served by the
	VPN identifier. The VPN identifier may be used to define the "VPN		VPN identifier. The VPN identifier may be used to define the "VPN
	authority" who is responsible for coordinating the connectivity and		authority" who is responsible for coordinating the connectivity and
	services employed by that VPN. The VPN authority may be the Private		services employed by that VPN. The VPN authority may be the Private
	Network administrator or the primary Service Provider. The VPN		Network administrator or the primary Service Provider. The VPN
	authority will administer and serve as the main point of contact for		authority will administer and serve as the main point of contact for
	the VPN. The authority may outsource some functions and		the VPN. The authority may outsource some functions and
	connectivity, set up contractual agreements with the different		connectivity, set up contractual agreements with the different
	Service Providers involved, and coordinate configuration,		Service Providers involved, and coordinate configuration,
End of changes. 2 change blocks.
	3 lines changed or deleted		5 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/