From routing-discussion-bounces@ietf.org  Wed Jan  5 19:37:27 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08187
	for <routing-discussion-archive@lists.ietf.org>; Wed, 5 Jan 2005 19:37:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmLa1-00012v-RA; Wed, 05 Jan 2005 19:32:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmLWT-0008TZ-BO
	for routing-discussion@megatron.ietf.org;
	Wed, 05 Jan 2005 19:29:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07684
	for <routing-discussion@ietf.org>; Wed, 5 Jan 2005 19:29:01 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmLj7-0003oh-Te
	for routing-discussion@ietf.org; Wed, 05 Jan 2005 19:42:11 -0500
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CmLWQ-000CPn-47
	for routing-discussion@ietf.org; Thu, 06 Jan 2005 00:29:02 +0000
Date: Wed, 5 Jan 2005 16:29:00 -0800
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1112699459.20050105162900@psg.com>
To: routing-discussion@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Subject: Review Call: draft-andersson-rtg-gmpls-change-00.txt
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Folks-

 We'd like to solicit your comments on this document before Last-Call'ing it.
 Please send your comments to the routing-discussion mailing list.

 http://www.ietf.org/internet-drafts/draft-andersson-rtg-gmpls-change-00.txt
 
                     MPLS and GMPLS Change Process
               draft-andersson-rtg-gmpls-change-00.txt
Abstract

   The MPLS and GMPLS protocol suites have become quite popular for a
   growing number of applications and deployment scenarios.  One result
   of this popularity is a large number of suggestions for modifications
   and extensions.

   The IETF needs to be flexible and responsive in how it handles these
   suggestions, and has a responsiblity to supervise the growth and
   evolution of MPLS and GMPLS protocols.

   This memo describes the process through which individuals, working
   groups and external standards bodies can influence the development of
   the MPLS and GMPLS standards.  This process means that extensions and
   changes to protocols specified by these working groups can only be
   made through the IETF, the body that created the (G)MPLS
   ((Generalized) Multiprotocol Label Switching) technologies.

-- 
Alex
http://www.psg.com/~zinin


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sun Jan  9 06:53:30 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07782
	for <routing-discussion-archive@lists.ietf.org>; Sun, 9 Jan 2005 06:53:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cnbb2-0008WC-0f; Sun, 09 Jan 2005 06:51:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CnbWq-00081h-Uc
	for routing-discussion@megatron.ietf.org;
	Sun, 09 Jan 2005 06:46:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07602
	for <routing-discussion@ietf.org>; Sun, 9 Jan 2005 06:46:38 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CnbkF-0003wX-7f
	for routing-discussion@ietf.org; Sun, 09 Jan 2005 07:00:31 -0500
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CnbWn-0001vz-53; Sun, 09 Jan 2005 11:46:37 +0000
Message-ID: <41E1199B.5040107@psg.com>
Date: Sun, 09 Jan 2005 12:46:35 +0100
From: dimitri papadimitriou <dpapadimitriou@psg.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.5) Gecko/20041217
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alex Zinin <zinin@psg.com>
References: <1112699459.20050105162900@psg.com>
In-Reply-To: <1112699459.20050105162900@psg.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: 7bit
Cc: routing-discussion@ietf.org
Subject: Re: Review Call: draft-andersson-rtg-gmpls-change-00.txt
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpapadimitriou@psg.com, dimitri.papadimitriou@alcatel.be
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
Content-Transfer-Encoding: 7bit

alex, several comments here below

1. section 2.4

"Traffic Engineering Working Group (te-wg).  These working
    groups have not specified any protocols, but have been a source of
    requirements to be considered by the (G)MPLS working groups."

that is not necessarily true - see "Protocol extensions for support of
Differentiated-Service-aware MPLS Traffic Engineering "

<http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-proto-08.txt>

2. section 3.2.1

"The mailing list to use will in most cases be the Routing Area maililng 
list, as this is the Area containing working group that has specified 
the protocol being changed and that will likely be the rewg. The IESG or 
the Routing Area ADs may decide to use a specific working group mailing 
list for this discussion."

so if well understand the routing area mailing list becomes the 
"default" starting point for most discussion ? but the question is that 
section 3.2.1 requires to write down a document detailing - ditto
"Anyone who intends to use one of the existing (G)MPLS protocols, but
thinks that it  will not satisfy their needs MUST write an Internet-
Draft (ID) explaining the problem they are trying to solve and why
the existing (G)MPLS  protocols will not work.  This Internet-Draft -
the problem statement ID - MUST include a detailed set of
requirements that (G)MPLS would need to meet to solve the particular 
problem." therefore is the targeted protocol not known before-hand 
making the above decision limited to a restricted number of problem 
statements rather than being the general case ? this comment seems 
in-line with the following section 2.3 statement "An entity or 
individual that wishes to propose extensions or changes to (G)MPLS 
should first decide to which Working Group (MPLS or CCAMP) it will bring 
the proposal." so why shall this discussion happen elsewhere ? any 
further clarification would be helpful here

3. section 3.2.4

"In this case the rewg will evaluate and refine the requirements,
merging them with other rewuirments if warranted. The result of
these deliberations will be captured in a requirements RFC."

as i understand the process for each "solution" we would now have a 
"requirement RFC" why is the usage of a motivation section in the 
solution document not considered for items with limited impact ?

4. section 5.

there are two classes of WG I-Ds/RFCs that are part of the (G)MPLS 
protocol suite that are not catalogued as outcome of the "(G)MPLS 
working groups" 1) routing extensions: RFC 3630, OSPFv3-TE, RFC 3784, 
GMPLS IS-IS TE and 2) the signaling protocol documents from which 
RSVP-TE has been derived but that still make abundantly usage of: RFC 
2205, 2210, 2961 (and to a less extend 2211, 2212, 2215) - are these 
part of the set mentioned in this section ?

5. General comment - does this document applies de-facto to new WGs that 
would potentially make use of the protocols of the (G)MPLS WGs such as 
the PCE WG for inst. (if the WG creation is approved), section 2.4 lists 
potential candidates but does not assume anythng specific for such 
situations

6. General comment - does this document assumes possible revision or 
refinment of the process based on its feedback and usage ?

7. edits: there are several typos in this document - for instance:

"One exeception to this rule is when other IETF working groups has
    been appointed, in accorance with the process descrbide in this
    document, to handled extensions and/or changes to the protocols
    specified by the MPLS working group."


Alex Zinin wrote:

> Folks-
> 
>  We'd like to solicit your comments on this document before Last-Call'ing it.
>  Please send your comments to the routing-discussion mailing list.
> 
>  http://www.ietf.org/internet-drafts/draft-andersson-rtg-gmpls-change-00.txt
>  
>                      MPLS and GMPLS Change Process
>                draft-andersson-rtg-gmpls-change-00.txt
> Abstract
> 
>    The MPLS and GMPLS protocol suites have become quite popular for a
>    growing number of applications and deployment scenarios.  One result
>    of this popularity is a large number of suggestions for modifications
>    and extensions.
> 
>    The IETF needs to be flexible and responsive in how it handles these
>    suggestions, and has a responsiblity to supervise the growth and
>    evolution of MPLS and GMPLS protocols.
> 
>    This memo describes the process through which individuals, working
>    groups and external standards bodies can influence the development of
>    the MPLS and GMPLS standards.  This process means that extensions and
>    changes to protocols specified by these working groups can only be
>    made through the IETF, the body that created the (G)MPLS
>    ((Generalized) Multiprotocol Label Switching) technologies.
> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Tue Jan 11 11:49:09 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08269
	for <routing-discussion-archive@lists.ietf.org>; Tue, 11 Jan 2005 11:49:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoP7P-0001ye-RP; Tue, 11 Jan 2005 11:43:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoP3J-0000Pg-MK
	for routing-discussion@megatron.ietf.org;
	Tue, 11 Jan 2005 11:39:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06976
	for <routing-discussion@ietf.org>; Tue, 11 Jan 2005 11:39:27 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoPH9-0000p4-Db
	for routing-discussion@ietf.org; Tue, 11 Jan 2005 11:53:48 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 11 Jan 2005 11:38:58 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0BGctm4012389; 
	Tue, 11 Jan 2005 11:38:55 -0500 (EST)
Message-Id: <200501111638.j0BGctm4012389@rtp-core-2.cisco.com>
To: Alex Zinin <zinin@psg.com>
In-reply-to: Your message of Wed, 05 Jan 2005 16:29:00 -0800.
	<1112699459.20050105162900@psg.com> 
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
	(=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
	(sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 11 Jan 2005 11:38:54 -0500
From: Eric Rosen <erosen@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: routing-discussion@ietf.org
Subject: Re: Review Call: draft-andersson-rtg-gmpls-change-00.txt 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org


I'll have to say that this document puzzles me quite a bit. 

It's already  true that nobody  can turn a  protocol extension into  an IETF
standard unless there is IETF consensus.  So I don't understand why any more
process is needed.

What  this  draft  seems  to  be  saying  is that  no  one  can  publish  an
Informational RFC  documenting a proprietary (or  non-IETF) extension unless
there is IETF consensus. 

That  seems very  foolish to  me.   Anyone who  wants to  deploy a  non-IETF
extension will  not be dissuaded from doing  so by the fact  that they can't
publish an RFC about it.  The only  effect of such a publication ban is that
it will be  a lot less convenient  for the IETF community to  find out about
it.  It's hard to see how this helps the IETF or the Internet. 

There  are a  number of  statements  about what  other SDOs  "MUST" do  when
extending IETF  protocols, but I don't  think the IETF has  any authority to
tell other SDOs what they "MUST" do. 

I  do think  it  makes sense,  within  the IETF,  to  require that  protocol
extensions  be approved  by  the WG  that  "owns" a  protocol,  even if  the
extensions  are  only  needed by  an  application  that  is specified  by  a
different WG.   However, I don't think we  need to add layers  and layers of
process here: one WG sends requirements to the other, then the other decided
whether they want to modify their charter, then the IESG decides whether the
charter should  be modified, then  solutions work begins from  scratch, etc.
Generally the first  WG will already have a  solution fairly well specified,
and usually the two WGs will have significant overlap in participation.  All
this process  then becomes nothing but  a waste of everyone's  time.  Not to
mention  becoming  another  oppportunity  to  introduce  politics,  marking,
inter-company rivalries, etc.

Sure,  the protocol-owning  WG should  be able  to critique  the  other WG's
solution, even  rejecting it if there  is good enough cause.   But let's not
have  a process  in which  we have  to pretend  that the  protocol-owning WG
should be starting the solutions work from scratch. 

>   The Pseudo Wire Emulation End to End (PWE3) working group is a
>   working in the Internet Area that also uses the (G)MPLS protocols in
>   its specifications.  Should the PWE3 specifications require extension
>   and/or changes to the (G)MPLS protocols these changes and/or
>   extensions SHALL be submitted to the (G)MPLS working group that
>   originally specified the protocol in the form of an Internet-Draft. 

This  is a  good  example.  PWE3  has  done a  fair amount  of  work on  LDP
extensions.  While  the LDP extensions need  to be approved by  the MPLS WG,
there is certainly  no need to start up a heavyweight  process in which PWE3
first has to send MPLS a requirements document! 

If you  make the process  too heavyweight, folks  will find a way  around it
anyway.  For  instance, instead of  specifying a new protocol  element, they
will just reinterpret an old one, and then claim that since there are no new
protocol  elements, there  has  been  no protocol  extension.   In terms  of
architectural  coherence, this  can be  much worse  than specifying  the new
protocol element. 





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jan 12 18:54:24 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00562
	for <routing-discussion-archive@lists.ietf.org>; Wed, 12 Jan 2005 18:54:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cos8F-0000H2-Nf; Wed, 12 Jan 2005 18:42:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoryI-0006mj-Q7
	for routing-discussion@megatron.ietf.org;
	Wed, 12 Jan 2005 18:32:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28950
	for <routing-discussion@ietf.org>; Wed, 12 Jan 2005 18:32:12 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CosCP-0003GV-Pc
	for routing-discussion@ietf.org; Wed, 12 Jan 2005 18:46:50 -0500
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CoryH-0006Fn-8R
	for routing-discussion@ietf.org; Wed, 12 Jan 2005 23:32:13 +0000
Date: Wed, 12 Jan 2005 15:32:12 -0800
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1194013165.20050112153212@psg.com>
To: routing-discussion@ietf.org
In-Reply-To: <200501122039.PAA12287@ietf.org>
References: <200501122039.PAA12287@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de
Content-Transfer-Encoding: 7bit
Subject: Fwd: [Pce] WG Action: Path Computation Element (pce)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
Content-Transfer-Encoding: 7bit

FYI.
-- 
Alex
http://www.psg.com/~zinin

This is a forwarded message
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce@ietf.org
Cc: pce@ietf.org
Date: Wednesday, January 12, 2005, 12:39:31 PM
Subject: [Pce] WG Action: Path Computation Element (pce)

===8<==============Original message text===============
A new IETF working group has been formed in the Routing Area. For additional 
information, please contact the Area Directors or the WG Chairs.

Path Computation Element (pce)
================================

Current Status: Active Working Group

Chair(s):
Adrian Farrel <adrian@olddog.co.uk>
JP Vasseur <jvasseur@cisco.com>

Routing Area Director(s):
Bill Fenner <fenner@research.att.com>
Alex Zinin <zinin@psg.com>

Routing Area Advisor:
Alex Zinin <zinin@psg.com>

Mailing Lists:
General Discussion: pce@ietf.org
To Subscribe: pce-request@ietf.org
In Body: subscribe pce
Archive: http://www.ietf.org/mail-archive/web/pce/

Description of Working Group:

The PCE Working Group is chartered to specify a Path Computation Element (PCE)
based architecture for the computation of paths for MPLS and GMPLS Traffic
Engineering LSPs.

In this architecture path computation does not occur on the head-end (ingress)
LSR, but on some other path computation entity that may physically not be
located on the head-end LSR.

The PCE WG will work on application of this model within a single domain
or within a small group of domains (where a domain is a layer, IGP area
or Autonomous System with limited visibility from the head-end LSR).
At this time, applying this model to large groups of domains such as the
Internet is not thought to be possible, and the PCE WG will not spend
energy on that topic.

The WG will specify a protocol for communication between LSRs (termed Path
Computation Clients - PCCs) and PCEs, and between cooperating PCEs. This
protocol will be capable of representing requests for path computation
including a full set of constraints, will be able to return multiple paths, and
will include security mechanisms such as authentication and confidentiality.

The WG will determine requirements for extensions to existing routing and
signaling protocols in support of PCE discovery and signaling of inter-domain
paths. Candidate protocols for extensions are RSVP-TE, OSPF-TE, ISIS-TE and
BGP. Any necessary extensions will be produced in collaboration with the
Working Groups responsible for the protocols.

The Working Group will also work on the definition of metrics to
evaluate path quality, scalability, responsiveness and robustness of
path computation models.

Work Items:

- Functional specification of MPLS and GMPLS Traffic Engineered LSP path
computation models involving Path Computation Element(s). This
includes the case of computing the paths of intra and inter-domain
TE LSPs. Such path computation includes the generation of primary,
protection and recovery paths, as well as computations for (local/global)
reoptimization and load balancing. The WG will address the inter-area
(single IGP domain) scenario first. WG progress will be evaluated before
inter-AS related work is started.

- Specification of the PCE-based architecture.

- Specification of requirements and protocol extensions related to
the policy, and security aspects of PCE-based path computation involving
PCEs of multiple administrative entities.

- In cooperation with protocol specific Working Group (OSPF, ISIS, IDR,
MPLS, CCAMP), development of routing (OSPF, ISIS, BGP) and LSP
signaling (RSVP-TE) extensions required to support PCE-based path
computation models.

- Specification of techniques in support of PCE discovery within and
across domains. Where such techniques result in the extensions of
existing protocols (e.g., OSPF, ISIS or BGP), this work will be done in
conjunction with the appropriate WGs.

- Specification of a new communication protocol for use between a PCC
and a PCE, and between PCEs. A single protocol will be selected from
among candidates that include the existing protocols defined in other
WGs.

- Definition of objective metrics to evaluate various criteria such as
the measurement of path quality, response time, robustness and
scalability of path computation models.

Review of the document "Requirements for path computation element in
GMPLS inter-domain networks" produced by the CCAMP WG.


Goals and Milestones:

Feb 05: Submit first draft of PCE architecture document

Feb 05: Submit first draft of PCE discovery requirements and protocol
extensions documents

Apr 05: Submit first draft of the PCE communication protocol
requirements

May 05: Submit first draft of the definition of objective metrics

Jul 05: Submit first draft of the PCE communication protocol
specification

Aug 05: Submit PCE architecture specification to the IESG to be
considered as Informational RFC

Nov 05: Submit first draft of applicability statement (describing the processes
and procedures for the use of the PCE architecture, protocols
and protocol extensions for inter-area MPLS and GMPLS Traffic
Engineering)

Nov 05: Submit first draft of the MIB module for the PCE protocol

Dec 05: Submit PCE communication protocol requirements to the IESG to be
considered as an Informational RFC

Dec 05: Submit PCE discovery protocol extensions specifications to the
IESG to be considered as a Proposed Standard

Dec 05: Submit PCE communication protocol specification to the IESG to
be considered as a Proposed Standard

Feb 06: Submit the applicability and metrics documents to the IESG to be
considered as Informational RFC

Feb 06: Evaluate WG progress, recharter or close.


_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

===8<===========End of original message text===========


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Fri Jan 14 15:03:46 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10164
	for <routing-discussion-archive@lists.ietf.org>; Fri, 14 Jan 2005 15:03:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpXSR-0000U2-Ki; Fri, 14 Jan 2005 14:50:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CpXO7-0007JC-BY
	for routing-discussion@megatron.ietf.org;
	Fri, 14 Jan 2005 14:45:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08844
	for <routing-discussion@ietf.org>; Fri, 14 Jan 2005 14:45:37 -0500 (EST)
Received: from kcmso1.att.com ([192.128.133.69] helo=kcmso1.proxy.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CpXcZ-0002Iy-N4
	for routing-discussion@ietf.org; Fri, 14 Jan 2005 15:00:38 -0500
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id
	j0EJhgoK019111
	for <routing-discussion@ietf.org>; Fri, 14 Jan 2005 13:45:04 -0600
Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by
	attrh5i.attrh.att.com (7.1.006)
	id 41C5B4F4004BB052; Fri, 14 Jan 2005 14:45:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 14 Jan 2005 13:45:03 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA060C85E4@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Review Call: draft-andersson-rtg-gmpls-change-00.txt
Thread-Index: AcTzh+J3z9qXZ96cS8qTc1qcGR/wWQG1JHLQ
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Alex Zinin" <zinin@psg.com>, <routing-discussion@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
Subject: RE: Review Call: draft-andersson-rtg-gmpls-change-00.txt
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Alex, All,

There was a very long thread in CCAMP on this I-D almost 2 years ago,
starts at:
http://ops.ietf.org/lists/ccamp/ccamp.2003/msg00072.html.  I posted a
few messages and made comments/suggestions then, however, I don't think
the comments were ever resolved/incorporated. =20

In essence, the suggestions I made were as follows:

1. In Section 3.2.2 "The MPLS and CCAMP working group chairs in
conjunction with the Area Directors will determine if the particular
problems raised ... should be evaluated by a working group... based on
the mailing list discussion."

Nothing is said as to criteria applied to the 'mailing list discussion'
(could be dominated by one loud person with a particular view), or how
the 'rewg will evaluate the problem statement'.  The decision process
appears to remain the status quo, i.e., 'rough consensus', which is not
particularly well defined and where sometimes a small group of key
people appear to 'decide' (especially problematic in 'no response'
decision).

Additional teeth could put in place to give a more comprehensive
review/decision process to overcome these identified problems, e.g., for
certain categories of problem statements/requirements, put a 'design
team' in place to evaluate/recommend a course of action.

Since the decision steps are quite vague, it would help to specify
criteria applied to the 'mailing list discussion' and how the 'rewg will
evaluate the problem statement'.  It seems that most any conclusion can
be reached with the process specified in the I-D.

2. In Section 3.2.4 "The rewg will evaluate the problem statement ID and
based on the evaluation make a recommendation to the IESG/IAB."

As a possible alternative/additional step in the decision process, put a
'design team' in place to evaluate/recommend a course of action, in some
cases where it might help the rewg.

Thanks,
Jerry

-----Original Message-----
From: routing-discussion-bounces@ietf.org
[mailto:routing-discussion-bounces@ietf.org] On Behalf Of Alex Zinin
Sent: Wednesday, January 05, 2005 7:29 PM
To: routing-discussion@ietf.org
Subject: Review Call: draft-andersson-rtg-gmpls-change-00.txt

Folks-

 We'd like to solicit your comments on this document before
Last-Call'ing it.
 Please send your comments to the routing-discussion mailing list.

=20
http://www.ietf.org/internet-drafts/draft-andersson-rtg-gmpls-change-00.
txt
=20
                     MPLS and GMPLS Change Process
               draft-andersson-rtg-gmpls-change-00.txt
Abstract

   The MPLS and GMPLS protocol suites have become quite popular for a
   growing number of applications and deployment scenarios.  One result
   of this popularity is a large number of suggestions for modifications
   and extensions.

   The IETF needs to be flexible and responsive in how it handles these
   suggestions, and has a responsiblity to supervise the growth and
   evolution of MPLS and GMPLS protocols.

   This memo describes the process through which individuals, working
   groups and external standards bodies can influence the development of
   the MPLS and GMPLS standards.  This process means that extensions and
   changes to protocols specified by these working groups can only be
   made through the IETF, the body that created the (G)MPLS
   ((Generalized) Multiprotocol Label Switching) technologies.

--=20
Alex
http://www.psg.com/~zinin


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sat Jan 22 18:05:24 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08494
	for <routing-discussion-archive@lists.ietf.org>; Sat, 22 Jan 2005 18:05:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CsUI0-0001jX-NF; Sat, 22 Jan 2005 18:03:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CsUGT-0000JC-NL
	for routing-discussion@megatron.ietf.org;
	Sat, 22 Jan 2005 18:01:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08284
	for <routing-discussion@ietf.org>; Sat, 22 Jan 2005 18:01:54 -0500 (EST)
Received: from corp.force10networks.com ([206.54.51.125]
	helo=mx.force10networks.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CsUWe-0000fv-HO
	for routing-discussion@ietf.org; Sat, 22 Jan 2005 18:18:40 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 22 Jan 2005 14:58:57 -0800
Message-ID: <B53A8EFF919E0A4BA9EC42775D99C47002EDE969@EXCH-CLUSTER-01.force10networks.com>
Thread-Topic: question on RFC1771 9.1.3
Thread-Index: AcUAsig+yH57/iWMSWeZ6Cc9tf5DFwAIp/sg
From: "Jason Chen" <jason@force10networks.com>
To: <routing-discussion@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Subject: question on RFC1771 9.1.3
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0463851887=="
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0463851887==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C500D5.F42A1F84"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C500D5.F42A1F84
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

=20

Hi,

=20

Can someone enlighten me on one paragraph on BGP RFC 1771 ?

=20

"   For the benefit of future support of inter-AS multicast
capabilities,
   a BGP speaker that participates in inter-AS multicast routing shall
   advertise a route it receives from one of its external peers and if
=20
=20
=20
Rekhter & Li                                                   [Page 38]
=20
RFC 1771                         BGP-4                        March 1995
=20
=20
   it installs it in its Loc-RIB, it shall advertise it back to the peer
   from which the route was received. For a BGP speaker that does not
   participate in inter-AS multicast routing such an advertisement is

   optional."

=20

I cannot figure out where it applied to and how it works? Is this
mandatory requirement for supporting MSDP?

=20

Appreciate for the help.

=20

Jason


------_=_NextPart_001_01C500D5.F42A1F84
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.emailstyle17
	{font-family:Arial;
	color:windowtext;}
span.EmailStyle19
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Can someone enlighten me on one paragraph on BGP RFC =
1771 ?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<pre><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>&#8220;</span></font>&nbsp;&=
nbsp; For the benefit of future support of inter-AS multicast =
capabilities,</pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; a BGP speaker that participates =
in inter-AS multicast routing shall</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; advertise a route it receives =
from one of its external peers and if</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Rekhter =
&amp; =
Li&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Page =
38]</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>RFC =
1771&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; =
BGP-4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
March 1995</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; it installs it in its Loc-RIB, =
it shall advertise it back to the peer</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; from which the route was =
received. For a BGP speaker that does not</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; participate in inter-AS =
multicast routing such an advertisement is</span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;&nbsp; optional.&#8221;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I cannot figure out where it applied to and how it works? Is =
this
mandatory requirement for supporting MSDP?</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Appreciate for the help.</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Jason</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C500D5.F42A1F84--


--===============0463851887==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============0463851887==--



From routing-discussion-bounces@ietf.org  Sat Jan 22 18:08:30 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08992
	for <routing-discussion-archive@lists.ietf.org>; Sat, 22 Jan 2005 18:08:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CsUI2-0001k0-5g; Sat, 22 Jan 2005 18:03:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CsUH5-0000tQ-Hr
	for routing-discussion@megatron.ietf.org;
	Sat, 22 Jan 2005 18:02:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08299
	for <routing-discussion@ietf.org>; Sat, 22 Jan 2005 18:02:32 -0500 (EST)
Received: from corp.force10networks.com ([206.54.51.125]
	helo=mx.force10networks.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CsUXG-0000gN-Hd
	for routing-discussion@ietf.org; Sat, 22 Jan 2005 18:19:18 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 22 Jan 2005 14:59:41 -0800
Message-ID: <B53A8EFF919E0A4BA9EC42775D99C47002EDE96A@EXCH-CLUSTER-01.force10networks.com>
Thread-Topic: question on RFC1771 9.1.3
Thread-Index: AcUAsig+yH57/iWMSWeZ6Cc9tf5DFwAI69CQ
From: "Jason Chen" <jason@force10networks.com>
To: <routing-discussion@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Subject: question on RFC1771 9.1.3
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1181967261=="
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1181967261==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C500D6.0E36B0D6"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C500D6.0E36B0D6
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

=20

Hi,

=20

Can someone enlighten me on one paragraph on BGP RFC 1771 ?

=20

"   For the benefit of future support of inter-AS multicast
capabilities,
   a BGP speaker that participates in inter-AS multicast routing shall
   advertise a route it receives from one of its external peers and if
=20
=20
=20
Rekhter & Li                                                   [Page 38]
=20
RFC 1771                         BGP-4                        March 1995
=20
=20
   it installs it in its Loc-RIB, it shall advertise it back to the peer
   from which the route was received. For a BGP speaker that does not
   participate in inter-AS multicast routing such an advertisement is

   optional."

=20

I cannot figure out where it applied to and how it works? Is this
mandatory requirement for supporting MSDP?

=20

Appreciate for the help.

=20

Jason


------_=_NextPart_001_01C500D6.0E36B0D6
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.emailstyle17
	{font-family:Arial;
	color:windowtext;}
span.EmailStyle19
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Can someone enlighten me on one paragraph on BGP RFC =
1771 ?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<pre><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>&#8220;</span></font>&nbsp;&=
nbsp; For the benefit of future support of inter-AS multicast =
capabilities,</pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; a BGP speaker that participates =
in inter-AS multicast routing shall</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; advertise a route it receives =
from one of its external peers and if</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Rekhter =
&amp; =
Li&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Page =
38]</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>RFC =
1771&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; =
BGP-4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
March 1995</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; it installs it in its Loc-RIB, =
it shall advertise it back to the peer</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; from which the route was =
received. For a BGP speaker that does not</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; participate in inter-AS =
multicast routing such an advertisement is</span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;&nbsp; optional.&#8221;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I cannot figure out where it applied to and how it works? Is =
this
mandatory requirement for supporting MSDP?</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Appreciate for the help.</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Jason</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C500D6.0E36B0D6--


--===============1181967261==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============1181967261==--



From routing-discussion-bounces@ietf.org  Mon Jan 24 12:53:34 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06003
	for <routing-discussion-archive@lists.ietf.org>; Mon, 24 Jan 2005 12:53:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ct8Eh-0004XI-8H; Mon, 24 Jan 2005 12:42:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ct80B-0001ts-Sv
	for routing-discussion@megatron.ietf.org;
	Mon, 24 Jan 2005 12:27:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03640
	for <routing-discussion@ietf.org>; Mon, 24 Jan 2005 12:27:44 -0500 (EST)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ct8Gi-0004Oz-Ov
	for routing-discussion@ietf.org; Mon, 24 Jan 2005 12:44:54 -0500
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id A1A4B2D483C; Mon, 24 Jan 2005 12:27:15 -0500 (EST)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 16560-01-38; Mon, 24 Jan 2005 12:27:14 -0500 (EST)
Received: from jhaas.nexthop.com (jhaas.nexthop.com [65.247.36.31])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 616522D4838; Mon, 24 Jan 2005 12:27:14 -0500 (EST)
Received: (from jhaas@localhost)
	by jhaas.nexthop.com (8.11.6/8.11.6) id j0OHREV06424;
	Mon, 24 Jan 2005 12:27:14 -0500 (EST)
Date: Mon, 24 Jan 2005 12:27:14 -0500
From: Jeffrey Haas <jhaas@nexthop.com>
To: Jason Chen <jason@force10networks.com>
Message-ID: <20050124172713.GG5850@nexthop.com>
References: <B53A8EFF919E0A4BA9EC42775D99C47002EDE96A@EXCH-CLUSTER-01.force10networks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B53A8EFF919E0A4BA9EC42775D99C47002EDE96A@EXCH-CLUSTER-01.force10networks.com>
User-Agent: Mutt/1.4.2.1i
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: routing-discussion@ietf.org
Subject: Re: question on RFC1771 9.1.3
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

Jason,

On Sat, Jan 22, 2005 at 02:59:41PM -0800, Jason Chen wrote:
> "   For the benefit of future support of inter-AS multicast
> capabilities,
>    a BGP speaker that participates in inter-AS multicast routing shall
>    advertise a route it receives from one of its external peers and if
>    it installs it in its Loc-RIB, it shall advertise it back to the peer
>    from which the route was received. For a BGP speaker that does not
>    participate in inter-AS multicast routing such an advertisement is
>    optional."

This was removed from the current BGP draft.

> I cannot figure out where it applied to and how it works? Is this
> mandatory requirement for supporting MSDP?

Draft-6 of MSDP used this information.  The current MSDP (RFC 3618)  doesn't.

-- 
Jeff Haas 
NextHop Technologies

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Mon Jan 31 21:46:10 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10651
	for <routing-discussion-archive@lists.ietf.org>; Mon, 31 Jan 2005 21:46:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cvo0y-0007me-00; Mon, 31 Jan 2005 21:43:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CqyLA-0007M3-EE
	for routing-discussion@megatron.ietf.org;
	Tue, 18 Jan 2005 13:44:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18951
	for <routing-discussion@ietf.org>; Tue, 18 Jan 2005 13:44:31 -0500 (EST)
Received: from web41013.mail.yahoo.com ([66.218.93.12])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CqyaN-00081c-P9
	for routing-discussion@ietf.org; Tue, 18 Jan 2005 14:00:22 -0500
Received: (qmail 41319 invoked by uid 60001); 18 Jan 2005 18:43:53 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	b=Ys+oZgCfLRVjIQ1T25R8CyAty7VRMw1IA/OXcZ1UvB7wH1h9wX/AzzEZa4PbwKXf2AWHx4XlWgKGB3q945m3R2hjbILDoHVTNTvASVdWytvUi3vt/szddVVz81LhTt3hGmTlFu9lT8Nbeft9T8GsZeVXVYg9C9Os2qKudljJ//o=
	; 
Message-ID: <20050118184353.41317.qmail@web41013.mail.yahoo.com>
Received: from [206.54.51.125] by web41013.mail.yahoo.com via HTTP;
	Tue, 18 Jan 2005 10:43:53 PST
Date: Tue, 18 Jan 2005 10:43:53 -0800 (PST)
From: je chen <je_chen@yahoo.com>
To: routing-discussion@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-Mailman-Approved-At: Mon, 31 Jan 2005 21:43:38 -0500
Subject: question on RFC1771
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

Hi,
I saw the below paragraph from BGP rfc. I think it is
related to MSDP but I cannot figure out what it means
and where it is applied to. Can someone help?

Thx,
jason


   "For the benefit of future support of inter-AS
multicast capabilities,
   a BGP speaker that participates in inter-AS
multicast routing shall
   advertise a route it receives from one of its
external peers and if
 
 
 
Rekhter & Li                                          
        [Page 38]
 
RFC 1771                         BGP-4                
       March 1995
 
 
   it installs it in its Loc-RIB, it shall advertise
it back to the peer
   from which the route was received. For a BGP
speaker that does not
   participate in inter-AS multicast routing such an
advertisement is
      optional."



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Mon Jan 31 21:49:24 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10866
	for <routing-discussion-archive@lists.ietf.org>; Mon, 31 Jan 2005 21:49:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cvo0y-0007mj-Dy; Mon, 31 Jan 2005 21:43:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CsQGn-000255-SS
	for routing-discussion@megatron.ietf.org;
	Sat, 22 Jan 2005 13:46:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23564
	for <routing-discussion@ietf.org>; Sat, 22 Jan 2005 13:46:00 -0500 (EST)
From: jasonchen@sbcglobal.net
Received: from smtp813.mail.sc5.yahoo.com ([66.163.170.83])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CsQWw-0004DY-5M
	for routing-discussion@ietf.org; Sat, 22 Jan 2005 14:02:43 -0500
Received: from unknown (HELO force10emd2lj9)
	(jasonchen@sbcglobal.net@69.104.61.42 with login)
	by smtp813.mail.sc5.yahoo.com with SMTP; 22 Jan 2005 18:45:58 -0000
To: <routing-discussion@ietf.org>
Date: Sat, 22 Jan 2005 10:42:43 -0800
Message-ID: <B53A8EFF919E0A4BA9EC42775D99C47002349BF9@EXCH-CLUSTER-01.force10networks.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 1.6 (+)
X-Scan-Signature: b8f3559805f7873076212d6f63ee803e
X-Mailman-Approved-At: Mon, 31 Jan 2005 21:43:38 -0500
Subject: question on RFC1771 9.1.3
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0579142674=="
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0579142674==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0000_01C5006F.28372680"

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01C5006F.28372680
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

 

Can someone enlighten me on one paragraph on BGP RFC 1771 ?

 

"   For the benefit of future support of inter-AS multicast
capabilities,
   a BGP speaker that participates in inter-AS multicast routing shall
   advertise a route it receives from one of its external peers and if
 
 
 
Rekhter & Li                                                   [Page 38]
 
RFC 1771                         BGP-4                        March 1995
 
 
   it installs it in its Loc-RIB, it shall advertise it back to the peer
   from which the route was received. For a BGP speaker that does not
   participate in inter-AS multicast routing such an advertisement is

   optional."

 

I cannot figure out where it applied to and how it works? Is this
mandatory requirement for supporting MSDP?

 

Appreciate for the help.

 

Jason


------=_NextPart_000_0000_01C5006F.28372680
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Can someone enlighten me on one paragraph on BGP RFC =
1771 ?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<pre><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>&#8220;</span></font>&nbsp;&=
nbsp; For the benefit of future support of inter-AS multicast =
capabilities,</pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; a BGP speaker that participates =
in inter-AS multicast routing shall</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; advertise a route it receives =
from one of its external peers and if</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Rekhter =
&amp; =
Li&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Page =
38]</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>RFC =
1771&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; =
BGP-4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
March 1995</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; it installs it in its Loc-RIB, =
it shall advertise it back to the peer</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; from which the route was =
received. For a BGP speaker that does not</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; participate in inter-AS =
multicast routing such an advertisement is</span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;&nbsp; optional.&#8221;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I cannot figure out where it applied to and how it works? Is =
this
mandatory requirement for supporting MSDP?</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Appreciate for the help.</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Jason</span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0000_01C5006F.28372680--



--===============0579142674==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============0579142674==--




From routing-discussion-bounces@ietf.org  Mon Jan 31 21:50:45 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11029
	for <routing-discussion-archive@lists.ietf.org>; Mon, 31 Jan 2005 21:50:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cvo0y-0007mo-SI; Mon, 31 Jan 2005 21:43:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CsVnU-000205-B7
	for routing-discussion@megatron.ietf.org;
	Sat, 22 Jan 2005 19:40:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13110
	for <routing-discussion@ietf.org>; Sat, 22 Jan 2005 19:40:04 -0500 (EST)
Received: from relay03.pair.com ([209.68.5.17])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CsW3e-0002Ku-Uz
	for routing-discussion@ietf.org; Sat, 22 Jan 2005 19:56:52 -0500
Received: (qmail 80747 invoked from network); 23 Jan 2005 00:40:05 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 23 Jan 2005 00:40:05 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	j0N0eEFV001169; Sat, 22 Jan 2005 19:40:14 -0500 (EST)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200501230040.j0N0eEFV001169@workhorse.faster-light.net>
To: "Jason Chen" <jason@force10networks.com>
In-reply-to: Your message of "Sat, 22 Jan 2005 14:58:57 PST."
	<B53A8EFF919E0A4BA9EC42775D99C47002EDE969@EXCH-CLUSTER-01.force10networks.com>
Date: Sat, 22 Jan 2005 19:40:14 -0500
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
X-Mailman-Approved-At: Mon, 31 Jan 2005 21:43:38 -0500
Cc: routing-discussion@ietf.org
Subject: Re: question on RFC1771 9.1.3 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@faster-light.net
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org


In message <B53A8EFF919E0A4BA9EC42775D99C47002EDE969@EXCH-CLUSTER-01.force10networks.com>
"Jason Chen" writes:
>  
>  
> Hi,
>  
> Can someone enlighten me on one paragraph on BGP RFC 1771 ?
>  
>    For the benefit of future support of inter-AS multicast capabilities,
>    a BGP speaker that participates in inter-AS multicast routing shall
>    advertise a route it receives from one of its external peers and if
>    it installs it in its Loc-RIB, it shall advertise it back to the peer
>    from which the route was received. For a BGP speaker that does not
>    participate in inter-AS multicast routing such an advertisement is
>    optional."
>  
> I cannot figure out where it applied to and how it works? Is this
> mandatory requirement for supporting MSDP?
>  
> Appreciate for the help.
>  
> Jason



Jason,

At the risk of being proven wrong ...

I think that is left over from the days of Multicast BGP and MOSPF.
I'm not sure if it is still needed.  In any case it doesn't hurt.  If
you don't use Multicast BGP, and no one does, then don't bother with
this advertisement.

Does anyone think this is needed?

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


