Re: [mpls-tp] Two additional MPLS TP requirements

Hi hopefully the requirement id we've done some time ago covers this requirement.

http://www.ietf.org/internet-drafts/draft-ietf-ccamp-pc-and-sc-reqs-06.txt

BR

Diego

__________________________________________
Diego Caviglia
Strategic Product Manager
Broadband Networks, PL Broadband Optical Network 
Ericsson Telecomunicazioni S.p.A. (TEI)
Via A. Negrone 1/A                           Office:  +39 010 600 3736
16153, Genova, Italy                          Fax: +39 010 600 3577
Block E Level 4                                  Mobile: +39 335 7181762
www.ericsson.com                       diego.caviglia@ericsson.com
This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.
________________________________

> -----Original Message-----
> From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
> Of Igor Bryskin
> Sent: martedì 31 marzo 2009 15.54
> To: Ben Niven-Jenkins; mpls-tp@ietf.org
> Subject: Re: [mpls-tp] Two additional MPLS TP requirements
> 
> Ben,
> Looks good to me. Just one comment: I think the requirement on the
> ownership transfer should be tighter: it must cause exactly 0 changes in
> the data plane to avoid any traffic hits.
> 
> Igor
> 
> -----Original Message-----
> From: Ben Niven-Jenkins [mailto:benjamin.niven-jenkins@bt.com]
> Sent: Tuesday, March 31, 2009 6:34 AM
> To: Igor Bryskin; mpls-tp@ietf.org
> Subject: Re: Two additional MPLS TP requirements
> 
> Igor,
> 
> Wrt requirement 1 I have added the following in the general requirements
> section
> 
> MPLS-TP MUST support the co-existence of statically and dynamically
> provisioned/managed MPLS-TP transport paths within the same layer network
> or
> domain.
> 
> Wrt requirement 2 I have added the following in the control plane
> requirements section
> 
> An MPLS-TP control plane MUST provide a mechanism for dynamic ownership
> transfer of the control of MPLS-TP transport paths from the management
> plane
> to the control plane and vice versa. The number of reconfigurations
> required
> in the data plane MUST be minimised (preferably no data plane
> reconfiguration will be required).
> 
> 
> I'm now not going to accept any new requirements otherwise we'll never get
> the document published.
> 
> Ben
> 
> 
> On 30/03/2009 15:03, "Igor Bryskin" <IBryskin@advaoptical.com> wrote:
> 
> > Ben, colleagues,
> >
> > I suggest adding two requirements to the MPLS-TP requirements document:
> >
> > 1. It must be possible for statically and dynamically
> provisioned/managed
> > MPLS-TP LSPs to co-exist in the same layer network;
> >
> > 2. MPLS-TP Control Plane must provide a mechanism for MPLS-TP LSP
> dynamic
> > ownership transfer from Management Plane to Control Plane and from
> Control
> > Plane to Management Plane with 0 reconfigurations in the Data Plane.
> >
> > The first requirement means, of course, that it must be possible for an
> > MPLS-TP layer network operator to setup and manage some LSPs via
> Management
> > Plane and some via Control Plane.
> >
> > The second requirement means that it must be possible for the operator
> to
> > statically provision an LSP and then have Control Plane to adopt the LSP
> (that
> > is, create CP state for the LSP that already exists in the DP), so that
> form
> > then on the LSP could managed (e.g. re-routed, modified, released, etc.)
> via
> > Control Plane. Likewise, it must be possible for the operator to use
> Control
> > Plane to dynamically setup an LSP, and once it is established have
> Control
> > Plane to abandon the LSP, so that from then on it would be
> indistinguishable
> > from the one that was statically setup.
> >
> > Opinions?
> >
> > Igor
> 
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp