RE: I-D ACTION:draft-chen-ccamp-ospf-interas-te-extension-01.txt

"Vijayanand C - TLS, Chennai." <vijayc@hcl.in> Mon, 05 February 2007 06:29 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HDxLg-0006To-Is for ccamp-archive@ietf.org; Mon, 05 Feb 2007 01:29:08 -0500
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HDxLf-0003Cg-1g for ccamp-archive@ietf.org; Mon, 05 Feb 2007 01:29:08 -0500
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1HDx6s-000Fzs-EX for ccamp-data@psg.com; Mon, 05 Feb 2007 06:13:50 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS, UNPARSEABLE_RELAY autolearn=ham version=3.1.7
Received: from [203.105.186.19] (helo=gws03.hcl.in) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from <vijayc@hcl.in>) id 1HDx6n-000FzK-QD for ccamp@ops.ietf.org; Mon, 05 Feb 2007 06:13:49 +0000
Received: from gws03.hcl.in (gws03 [10.249.64.134]) by localhost.hcl.in (Postfix) with ESMTP id 0884D37C00A; Mon, 5 Feb 2007 11:43:42 +0530 (IST)
Received: from chn-egw01-out.corp.hcl.in (unknown [10.249.64.37])by gws03.hcl.in (Postfix) with ESMTPid DB1C437C056; Mon, 5 Feb 2007 11:43:41 +0530 (IST)
Received: from CHN-HCLT-EVS02.HCLT.CORP.HCL.IN ([10.101.26.15]) by chn-egw01-out.corp.hcl.in with Microsoft SMTPSVC(6.0.3790.1830); Mon, 5 Feb 2007 11:43:41 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: I-D ACTION:draft-chen-ccamp-ospf-interas-te-extension-01.txt
Date: Mon, 05 Feb 2007 11:42:43 +0530
Message-ID: <D309264CD3651841AA75658A61044758483C75@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: I-D ACTION:draft-chen-ccamp-ospf-interas-te-extension-01.txt
Thread-Index: AcdHBYNpfs4FSs0pQyGUfyhshRyCiQB5qwzQ
From: "Vijayanand C - TLS, Chennai." <vijayc@hcl.in>
To: Adrian Farrel <adrian@olddog.co.uk>, Mach Chen <mach@huawei.com>
Cc: ccamp@ops.ietf.org
X-OriginalArrivalTime: 05 Feb 2007 06:13:41.0579 (UTC) FILETIME=[C872B1B0:01C748EC]
X-imss-version: 2.046
X-imss-result: Passed
X-imss-scanInfo: M:T L:E SM:1
X-imss-tmaseResult: TT:1 TS:-27.2685 TC:1F TRN:94 TV:3.6.1039(14974.003)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:2 C:2 M:2 S:2 R:2 (0.0000 0.0000)
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f0b5a4216bfa030ed8a6f68d1833f8ae


In atleast one network that I know of, there are inter-AS links which
are multi-access ( GigE links connected by switches), but currently not
enabled for TE because TE is not deployed in the network. But if the TE
is deployed in this network then the inter-AS link will become a TE
link.

Regards
Vijay

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Saturday, February 03, 2007 1:35 AM
> To: Mach Chen; Vijayanand C - TLS, Chennai.
> Cc: ccamp@ops.ietf.org
> Subject: Re: I-D
ACTION:draft-chen-ccamp-ospf-interas-te-extension-01.txt
> 
> Hmmm.
> 
> Question: Does anyone use multi-access TE links between ASes?
> 
> If so, we should address them (probably the same way that we address
them
> within an AS/area - that is by defining a separate link type). But if
no-
> one
> uses them, then we should leave that definition until there is a need.
> 
> I see that section 3.2 of Mach's I-D is very explicit that the new
link
> type
> is p2p, so that is good.
> 
> Cheers,
> Adrian
> ----- Original Message -----
> From: "Mach Chen" <mach@huawei.com>
> To: "Vijayanand C - TLS, Chennai." <vijayc@hcl.in>
> Cc: <ccamp@ops.ietf.org>
> Sent: Friday, February 02, 2007 10:19 AM
> Subject: Re: I-D
ACTION:draft-chen-ccamp-ospf-interas-te-extension-01.txt
> 
> 
> > Hi vijay,
> >
> > First, thanks for your questions.
> >
> > So far this version doesn't mention inter-as multi-access links, an
> > alternative method, as you said,
> > of describing this kind of links is to treat them as multiple P2P
links.
> I
> > will supplement this description
> > in the future revised version.
> >
> > Best regards,
> >
> > Mach
> >
> > ----- Original Message -----
> > From: "Vijayanand C - TLS, Chennai." <vijayc@hcl.in>
> > To: "Mach Chen" <mach@huawei.com>; <ccamp@ops.ietf.org>
> > Sent: Friday, February 02, 2007 3:30 PM
> > Subject: RE: I-D ACTION:draft-chen-ccamp-ospf-interas-te-extension-
> 01.txt
> >
> >
> >
> > The draft does not seem to address multi-access links between ASes.
> > Should the inter-AS link only be a point to point link or you are
trying
> > to model multi-access links as multiple P2P links ( in which case
B.W
> > calculations etc would not be straightforward)
> >
> >
> >
> > Regards
> > Vijay
> >
> >> -----Original Message-----
> >> From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On
> > Behalf
> >> Of Mach Chen
> >> Sent: Friday, February 02, 2007 6:49 AM
> >> To: ccamp@ops.ietf.org
> >> Subject: Fw: I-D
> > ACTION:draft-chen-ccamp-ospf-interas-te-extension-01.txt
> >>
> >> Hi,
> >>
> >> We have just submitted the second revision of our
> > I-D,draft-chen-ccamp-
> >> ospf-interas-te-extensions.
> >>
> >> The problem we are trying to solve is how a PCE or entry-point ASBR
> > can
> >> select the exit-point ASBR for a TE LSP when it knows (from the
ERO)
> > the
> >> downstream AS or the downstream ASBR. We believe that IGP needs to
> > flood
> >> the inter-AS TE links together with additional information about
the
> >> neighboring AS and ASBR. The problem arises for both the pd-path
and
> > brpc
> >> computation methods.
> >>
> >> We would welcome your input on our problem statement and our
proposed
> >> solution.
> >>
> >> Best regards,
> >>
> >> Mach & Renhai
> >>
> >> ----- Original Message -----
> >> From: <Internet-Drafts@ietf.org>
> >> To: <i-d-announce@ietf.org>
> >> Sent: Friday, February 02, 2007 4:50 AM
> >> Subject: I-D
ACTION:draft-chen-ccamp-ospf-interas-te-extension-01.txt
> >>
> >>
> >> >A New Internet-Draft is available from the on-line Internet-Drafts
> >> > directories.
> >> >
> >> >
> >> > Title : OSPF Extensions in Support of Inter-AS (G)MPLS TE
> >> > Author(s) : M. Chen, R. Zhang
> >> > Filename : draft-chen-ccamp-ospf-interas-te-extension-01.txt
> >> > Pages : 11
> >> > Date : 2007-2-1
> >> >
> >> > This document describes extensions to the OSPF protocol to
support
> >> >   Multiprotocol Label Switching (MPLS) and Generalized MPLS
(GMPLS)
> >> >   Traffic Engineering (TE) for multiple Autonomous Systems
(ASes).
> > It
> >> >   defines OSPF extensions for the flooding of inter-AS links
which
> > can
> >> >   be used to perform inter-AS path computation.
> >> >
> >> > A URL for this Internet-Draft is:
> >> >
> >
http://www.ietf.org/internet-drafts/draft-chen-ccamp-ospf-interas-te-
> >> extension-01.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-chen-ccamp-ospf-interas-te-extension-01.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-chen-ccamp-ospf-interas-te-extension-
> >> 01.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.
> >> >
> >>
> >>
> >>
> >
------------------------------------------------------------------------
> > --
> >> ------
> >>
> >>
> >> > _______________________________________________
> >> > I-D-Announce mailing list
> >> > I-D-Announce@ietf.org
> >> > https://www1.ietf.org/mailman/listinfo/i-d-announce
> >> >
> >
> >
> >
> >
> >
> 


DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in 
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of 
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender immediately. Before opening any mail and 
attachments please check them for viruses and defect.

-----------------------------------------------------------------------------------------------------------------------