[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: I-D ACTION:draft-farrel-ccamp-inter-domain-framework-00.txt
Hi Everyone,
I have a couple of questions or comments on this draft.
1) Does this draft cover requirements described in draft-ietf-tewg-interas-
mpls-te-req-06.txt ?
2) Although this draft describes the framework in not only MPLS but
also GMPLS, the content mainly focuses on MPLS. For example of
As pointed out by Dimitri, this should focus on automated stitching,
referring to GMPLS e2e recovery drafts.
3) In this draft, the architecture using PCE is assumed. I do not deny
this description in MPLS, but I feel unnatural in the case of GMPLS.
4) In terms of Inter-domain OAM, RRO processing may also be clarified
on this draft from the point of route management.
5) Considering the overall, I feel unclear about the difference between
requirement draft and the framework draft. Could you clarify this?
6) I propose to have a separate framework draft of MPLS as well as
GMPLS.
Regards,
tomo
----------------------------------------
Tomohiro Otani
KDDI R&D Laboratories, Inc.
----------------------------------------
At 22:08 04/05/11 +0200, dimitri papadimitriou wrote:
>hi adrian,
>
>Adrian Farrel wrote:
>
> > Folks,
> >
> > This draft represents the first step in the much-discussed six point
> > plan towards inter-area/AS solutions.
> >
> > I would like three things to happen:
> >
> > a. This draft to become a WG draft
> > Please send your opinions
>
>i think this is a good start
>
> > b. The draft to be reinforced in areas that people consider necessary
> > One such area MAY be diverse routing.
> > Please send suggested text, but
> > - recall that this is not a solutions draft
> > - try to keep the length of the draft down below 100 pages
>
>i think the draft should focus on automated stitching and more advanced
>features like inter-domain recovery and crankback signaling
>
>this said the document points out a very interesting concept of multi-
>domain FA (since so far the concept has been detailed in the context of
>a single area and TE link) - imho it would be worth reinforcing also this
part of the document as well, if that was the intention -
>
> > c. Move on with the next step in the plan.
> > At the moment, this seems to require effort on points 2 and 4
> > Viz, develop individual signaling solutions as required and
> > state their applicability.
> > We await input from those who have preferred solutions.
> >
> > Cheers,
> > Adrian
> > ----- Original Message -----
> > From: <Internet-Drafts@ietf.org>
> > To: <i-d-announce@ietf.org>
> > Cc: <ccamp@ops.ietf.org>
> > Sent: Friday, April 30, 2004 8:44 PM
> > Subject: I-D ACTION:draft-farrel-ccamp-inter-domain-framework-00.txt
> >
> >
> >
> >>A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> >>
> >>
> >>Title : A Framework for Inter-Domain MPLS Traffic Engineering
> >>Author(s) : A. Farrel, et al.
> >>Filename : draft-farrel-ccamp-inter-domain-framework-00.txt
> >>Pages : 14
> >>Date : 2004-4-30
> >>
> >>This document provides a framework for establishing and controlling
> >> Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
> >> Label Switched Paths (LSPs) in multi-domain networks.
> >>
> >> For the purposes of this document, a domain is considered to be any
> >> collection of network elements within a common sphere of address
> >> management or path computational responsibility. Examples of such
> >> domains include IGP areas and Autonomous Systems.
> >>
> >>A URL for this Internet-Draft is:
>
>>http://www.ietf.org/internet-drafts/draft-farrel-ccamp-inter-domain-framework-00.txt
> >>
> >>To remove yourself from the I-D Announcement list, send a message to
> >>i-d-announce-request@ietf.org with the word unsubscribe in the body
of the message.
> >>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> >>to change your subscription settings.
> >>
> >>
> >>Internet-Drafts are also available by anonymous FTP. Login with the username
> >>"anonymous" and a password of your e-mail address. After logging in,
> >>type "cd internet-drafts" and then
> >>"get draft-farrel-ccamp-inter-domain-framework-00.txt".
> >>
> >>A list of Internet-Drafts directories can be found in
> >>http://www.ietf.org/shadow.html
> >>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>
> >>
> >>Internet-Drafts can also be obtained by e-mail.
> >>
> >>Send a message to:
> >>mailserv@ietf.org.
> >>In the body type:
> >>"FILE /internet-drafts/draft-farrel-ccamp-inter-domain-framework-00.txt".
> >>
> >>NOTE: The mail server at ietf.org can return the document in
> >>MIME-encoded form by using the "mpack" utility. To use this
> >>feature, insert the command "ENCODING mime" before the "FILE"
> >>command. To decode the response(s), you will need "munpack" or
> >>a MIME-compliant mail reader. Different MIME-compliant mail readers
> >>exhibit different behavior, especially when dealing with
> >>"multipart" MIME messages (i.e. documents which have been split
> >>up into multiple messages), so check your local documentation on
> >>how to manipulate these messages.
> >>
> >>
> >>Below is the data which will enable a MIME compliant mail reader
> >>implementation to automatically retrieve the ASCII version of the
> >>Internet-Draft.
>
>