withmilestones-00-00.txt		withmilestones-00-01.txt
	The SPRING working group will define procedures that will allow		The SPRING working group will define procedures that will allow
	a node to steer a packet between any source and destination through		a node to steer a packet along an explicit route through
	a SPRING region on any path without requiring state to be		the SPRING region without requiring path state to be
	maintained by transited nodes, but rather at the source device. A		maintained by transited nodes. A SPRING region is a network
	SPRING region is a network comprised of nodes (which may be of		comprised of nodes (which may be of any type, including
	any type, including routers and appliances) that share the following		routers and appliances) that share the following
	trust model: any node in the SPRING region is trusted to steer		trust model: any node in the SPRING region is trusted to steer
	a packet through any of the other nodes within the region. The		a packet along any path within the region. Steering is
	SPRING region may comprise one or more ASes, or even less than a		achieved by specifying in the packet an ordered set of
	single AS. Although a region may comprise more than one AS, initial		nodes and/or links and/or shortest-path-next-hops to be
	work will focus on the intra-domain, that is, single AS, scenario.		traversed by the packet. The SPRING region may comprise one
			or more ASes, or even less than a single AS. Although a
			region may comprise more than one AS, initial work will
			focus on the intra-domain, that is, single AS, scenario.
	The procedures should support both centralised and distributed path		The procedures should support both centralised and distributed path
	computation. The procedures should also cover support for OAM		computation. The procedures should also cover support for OAM
	functions.		functions.
	Where use cases are documented, care should be taken to define the		Where use cases are documented, care should be taken to define the
	data plane requirements for the environment within which they are		data plane requirements for the environment within which they are
	to be implemented. The procedures should avoid modifications to		to be implemented. The procedures should avoid modifications to
	the MPLS data plane, in order to remain compatible with existing		the MPLS data plane, in order to remain compatible with existing
	extensive deployments of MPLS. It is anticipated that the procedures		extensive deployments of MPLS. It is anticipated that the procedures
	may require modifications to the IPv6 data plane. While the initial		may require modifications to the IPv6 data plane. While the initial
	focus of the SPRING WG is on the intra-domain deployment scenarios		focus of the SPRING WG is on the intra-domain deployment scenarios
	(see below), the modifications to the IPv6 data plane must support		(see below), the modifications to the IPv6 data plane must support
	both intra and inter-domain deployment scenarios.		both intra and inter-domain deployment scenarios.
			Where possible, existing protocols must be used to implement the
			SPRING function. Any modification or extension of existing architectures
			or protocols must be carried out in the working groups responsible for
			the architectures or protocols being modified in co-ordination with
			this working group, but may be done in this working group after
			agreement with all the relevant WG chairs and responsible ADs
	The SPRING working group is chartered for the following list of		The SPRING working group is chartered for the following list of
	items:		items:
	o Identification and evaluation of use cases for which there		o Identification and evaluation of use cases for which there
	is consensus within the WG.		is consensus within the WG.
	o Definition of new procedures, driven by the use cases and underlying		o Definition of new procedures, driven by the use cases and underlying
	technology. The new procedures must cover security considerations		technology. The new procedures must cover security considerations
	(including the relationship between networks forming the SPRING		(including the relationship between networks forming the SPRING
	region) and allow for solutions which substantially improve upon		region) and allow for solutions which substantially improve upon
	current technologies by defining requirements, extensions, or new		current technologies by defining requirements, extensions, or new
	functionality in existing routing, management or other protocols.		functionality in existing routing, management or other protocols.
	o Determine whether the above mentioned procedures require		o Determine whether the above mentioned procedures require
	modification/changes to the existing MPLS architecture, and		modification/changes to the existing MPLS architecture, and
	if so, then document such modifications/changes.		if so, then document requirements for such modifications/changes.
	o Determine whether the above mentioned procedures require		o Determine whether the above mentioned procedures require
	modification/changes to the existing IPv6 architecture, and		modification/changes to the existing IPv6 architecture, and
	if so, then document such modifications/changes.		if so, then document requirements for such modifications/changes.
	o The SPRING working group will then develop solutions, focusing		o The SPRING working group will then develop solutions, focusing
	initially on intra-domain deployment scenarios. Where such		initially on intra-domain deployment scenarios. Where such
	solutions utilize existing protocols (IS-IS, OSPF, BGP, PCE) this will		solutions utilize existing protocols (IS-IS, OSPF, BGP, PCE) this will
	be done in conjunction with the responsible IETF working group. Work		be done in conjunction with the responsible IETF working group. Work
	on new protocols may be carried out by the SPRING working group.		on new protocols may be carried out by the SPRING working group.
	The working group will develop the following documents:		The working group will develop the following documents:
	o One or more documents describing SPRING use cases,		o One or more documents describing SPRING use cases,
	o Specification of new procedures to support SPRING use cases,		o Specification of new procedures to support SPRING use cases,
	o Changes to MPLS architecture, if needed		o Requirements for changes to MPLS architecture, if needed,
	o Changes to IPv6 architecture, if needed		o Requirements for changes to IPv6 architecture, if needed,
	o Document interworking and co-existence between the new procedures		o Document interworking and co-existence between the new procedures
	and the existing MPLS signaling protocols (LDP, RSVP-TE, BGP),		and the existing MPLS signaling protocols (LDP, RSVP-TE, BGP),
	o Document impact (if any) of any proposed IPv6 data plane modifications		o Document impact (if any) of any proposed IPv6 data plane modifications
	on existing deployment of IPv6,		on existing deployment of IPv6,
	o A set of one or more protocol extensions requirements documents,		o A set of one or more protocol extensions requirements documents,
	o Inter-operability reports pertaining to the implementation of extensions		o Inter-operability reports pertaining to the implementation of extensions
	supporting SPRING.		supporting SPRING.
	Milestones		Milestones
End of changes. 6 change blocks.
	13 lines changed or deleted		22 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/