
From tme@americafree.tv  Wed May 13 11:19:32 2009
Return-Path: <tme@americafree.tv>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE55D3A6CB1 for <l3vpn@core3.amsl.com>; Wed, 13 May 2009 11:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.234
X-Spam-Level: 
X-Spam-Status: No, score=-2.234 tagged_above=-999 required=5 tests=[AWL=-0.235, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGfm6pqWxUIz for <l3vpn@core3.amsl.com>; Wed, 13 May 2009 11:19:31 -0700 (PDT)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 005B63A6AB2 for <l3vpn@ietf.org>; Wed, 13 May 2009 11:19:30 -0700 (PDT)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 1C73B3CAE0D9 for <l3vpn@ietf.org>; Wed, 13 May 2009 14:21:03 -0400 (EDT)
Message-Id: <0E18C5B4-8C3B-4E62-81DC-A5C98864FB06@americafree.tv>
From: Marshall Eubanks <tme@americafree.tv>
To: l3vpn@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Fwd: 75th IETF - WG/BOF Scheduling 
Date: Wed, 13 May 2009 14:21:02 -0400
References: <20090513180513.6619B28C203@core3.amsl.com>
X-Mailer: Apple Mail (2.930.3)
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2009 18:19:32 -0000

Note well. We have already put in for meeting time.

Marshall

Begin forwarded message:

> From: IETF Agenda <agenda@ietf.org>
> Date: May 13, 2009 2:05:13 PM EDT
> To: Working Group Chairs <wgchairs@ietf.org>
> Cc: irsg@isi.edu, bofchairs@ietf.org
> Subject: 75th IETF - WG/BOF Scheduling
>
> -----------------------------------------------------------------
> 75th IETF =96 Stockholm, Sweden
> Meeting Dates: July 26-31, 2009
> Host: .SE
> -----------------------------------------------------------------
> IETF meetings start Monday morning and run through Friday mid-=20
> afternoon
> (15:15).
>
> We are accepting scheduling requests for all Working Groups and BOFs
> starting.  The milestones and deadlines for scheduling-related =20
> activities
> are as follows:
>
> NOTE: cutoff dates are subject to change.
>
> May 25, Monday - Cutoff date for requests to schedule Working Group
> meetings and for preliminary BOF proposals to ADs at 17:00 PDT (24:00
> UTC/GMT).
> June 8, Monday - Cutoff date for requests to Area Directors to =20
> schedule
> BOFs at 17:00 PDT (24:00 UTC/GMT).
> June 15, Monday - Cutoff date for Area Directors to approve BOFs at =20=

> 17:00
> PDT (24:00 UTC/GMT).
> June 19, Friday - Preliminary agenda published for comment.
> July 1, Wednesday - Cutoff date for requests to reschedule Working =20
> Group
> and BOF meetings 17:00 PDT (24:00 UTC/GMT).
> July 6, Monday - Final agenda to be published.
> July 15, Wednesday - Draft Working Group agendas due by 17:00 PT =20
> (24:00
> UTC/GMT).
> July 20, Monday - Revised Working Group agendas due by 17:00 PT (24:00
> UTC/GMT).
>
> Submitting Requests for Working Group and BOF Sessions
>
> Please submit requests to schedule your Working Group sessions using =20=

> the
> "IETF Meeting Session Request Tool," a Web-based tool for submitting =20=

> all
> of the information that the Secretariat requires to schedule your
> sessions.
>
> The URL for the tool is:
>
> https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi
>
> Instructions for using the tool are available at:
>
> http://www.ietf.org/instructions/session_request_tool_instruction.html
>
> Please send requests to schedule your BOF sessions to agenda@ietf.org.
> Please include the acronym of your BOF in the subject line of the =20
> message,
> and include all of the information specified in item (4) of =20
> "Requesting
> Meeting Sessions at IETF Meetings" in the body.  (This document is
> included below.)
>
> Submitting Session Agendas
>
> For the convenience of meeting attendees, we ask that you submit the
> agendas for your Working Group sessions as early as possible.  Draft
> Working Group agendas are due Wednesday, July 15 by 17:00 PDT (24:00
> UTC/GMT).  Revised Working Group agendas are due no later than Monday,
> July 20 at 17:00 PDT (24:00 UTC/GMT).  The proposed agenda for a BOF
> session should be submitted along with your request for a session.  =20=

> Please
> be sure to copy your Area Director on that message.
>
> Please submit the agendas for your Working Group sessions using the =20=

> "IETF
> Meeting Materials Management Tool," a Web-based tool for making your
> meeting agenda, minutes, and presentation slides available to the
> community before, during, and after an IETF meeting.  If you are a BOF
> chair, then you may use the tool to submit a revised agenda as well as
> other materials for your BOF once the BOF has been approved.
>
> The URL for the tool is:
>
> https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi
>
> Additional information about this tool is available at:
>
> http://www.ietf.org/instructions/meeting_materials_tool.html
>
> Agendas submitted via the tool will be available to the public on the
> "IETF Meeting Materials" Web page as soon as they are submitted.
>
> The URL for the "IETF 75 Meeting Materials" Web page is:
>
> =
https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=3D75=

>
> If you are a Working Group chair, then you already have accounts on =20=

> the
> "IETF Meeting Session Request Tool" and the "IETF Meeting Materials
> Management Tool."  The same User ID and password will work for both =20=

> tools.
>  If you are a BOF chair who is not also a Working Group chair, then =20=

> you
> will be given an account on the "IETF Meeting Materials Management =20
> Tool"
> when your BOF has been approved.  If you require assistance in using
> either tool, or wish to report a bug, then please send a message to:
> ietf-action@ietf.org.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> For your convenience, comprehensive information on requesting meeting
> sessions at IETF 75 is presented below:
>
> 1. Requests to schedule Working Group sessions should be submitted =20
> using
> the "IETF Meeting Session Request Tool," a Web-based tool for =20
> submitting
> all of the information required by the Secretariat to schedule your
> sessions.  The URL for the tool is:
>
> https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi
>
> Instructions for using the tool are available at:
>
> http://www.ietf.org/instructions/session_request_tool_instruction.html
>
> If you require an account on this tool, or assistance in using it, =20
> then
> please send a message to ietf-action@ietf.org.  If you are unable to =20=

> use
> the tool, then you may send your request via e-mail to =20
> agenda@ietf.org,
> with a copy to the appropriate Area Director(s).
>
> Requests to schedule BOF sessions must be sent to agenda@ietf.org =20
> with a
> copy to the appropriate Area Director(s).
>
> When submitting a Working Group or BOF session request by e-mail, =20
> please
> include the Working Group or BOF acronym in the Subject line.
>
> 2. BOFs will NOT be scheduled unless the Area Director(s) approved
> request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, =20
> CHAIR(S)
> NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL
> DESCRIPTION, and the information requested in (4) below. (Please =20
> read the
> BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt before
> requesting a session for a BOF.)
>
> 3. A Working Group may request either one or two sessions.  If your
> Working Group requires more than two sessions, then your request =20
> must be
> approved by an Area Director.  Additional sessions will be assigned, =20=

> based
> on availability, after Wednesday, July 1 at 17:00 PDT (24:00 UTC/=20
> GMT), the
> cut-off date for requests to reschedule a session.
>
> 4. You MUST provide the following information before a Working Group =20=

> or
> BOF session will be scheduled:
>
>    a. Working Group or BOF full name with acronym in brackets:
>
>    b. AREA under which Working Group or BOF appears:
>
>    c. CONFLICTS you wish to avoid, please be as specific as possible:
>
>    d. Expected Attendance (figures from the 74th IETF meeting are
> included at the end of this message):
>
>    e. Special requests:
>
>    f. Number of sessions:
>
>    g. Length of session:
>       - 1 hour
>       - 1 1/2 hours
>       - 2 hours
>       - 2 1/2 hours
>
> For more information on scheduling Working Group and BOF sessions, =20
> please
> refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and =20
> Procedures"
> (http://www.ietf.org/rfc/rfc2418.txt).
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> For your convenience please find here a list of the IETF Area =20
> Directors
> with their e-mail addresses:
>
> IETF Chair
> Russ Housley <housley@vigilsec.com>
>
> Applications Area (app)
> Lisa Dusseault <lisa.Dusseault@messagingarchitects.com>
> Alexey Melnikov <alexey.melnikov@isode.com>
>
> Internet Area (int)
> Jari Arkko <jari.arkko@piuha.net>
> Ralph Droms <rdroms@cisco.com>
>
> Operations & Management Area (ops)
> Ronald Bonica <rbonica@juniper.net>
> Dan Romascanu <dromasca@avaya.com>
>
> Real-time Applications and Infrastructure Area (rai)
> Cullen Jennings <fluffy@cisco.com>
> Robert Sparks <rjsparks@nostrum.com>
>
> Routing Area (rtg)
> Ross Callon <rcallon@juniper.net>
> Adrian Farrel <adrian.farrel@huawei.com>
>
> Security Area (sec)
> Pasi Eronen <pasi.eronen@nokia.com>
> Tim Polk <tim.polk@nist.gov>
>
> Transport Area (tsv)
> Lars Eggert <lars.eggert@nokia.com>
> Magnus Westerlund <magnus.westerlund@ericsson.com>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 74th IETF Meeting Attendance Number
>
> 6ai	189
> 6lowpan	NO SHEETS
> 6man	138
> alto 	112
> ancp	21
> apparea (AG)	92
> atoca	77
> autoconf	34
> avt	77
> avt (2nd session)	65
> behave	150
> behave (2nd session)	116
> bliss	64
> bmwg	23
> capwap	16
> ccamp	76
> ccamp (2nd session)	55
> csi	16
> dccp	18
> dhc	50
> dime	31
> dkim	46
> dnsop	90
> drinks	69
> dtnrg (RG)	44
> ecrit	80
> emu	35
> fecframe	17
> forces	20
> geopriv	68
> grow	75
> hiprg (RG)	38
> hokey	40
> httpbis 	25
> idnabis	70
> idnabis (2nd session)	41
> idr	127
> intarea (AG)	207
> ipfix	32
> ippm	46
> ipsecme	44
> isms	25
> keyprov	24
> kitten	11
> krb-wg	26
> l2vpn	149
> l3vpn	48
> ledbat	30
> lisp	176
> manet	45
> mboned	37
> mediactrl	47
> mext	96
> mif	68
> mip4	35
> mipshop	57
> mmox	77
> mmusic	75
> morg	15
> mpls	144
> mpls (2nd session)	135
> msec	30
> nea	28
> netconf	39
> netext	68
> netmod	25
> netmod (2nd session)	32
> nfsv4	22
> nsis	23
> oauth	105
> opsarea (AG)	86
> opsec	24
> ospf	34
> p2prg	99
> p2psip	71
> pce	63
> pcn	24
> pim	41
> pkix	50
> pmol	27
> pre8prob	44
> pwe3	115
> radext	19
> rtgarea (AG)	122
> rmt	12
> roll	69
> rrg (RG)	106
> rtgwg	112
> saag (AG)	116
> sasl	24
> savi	60
> shara	155
> sidr	77
> sieve	17
> simple	69
> sip	126
> sip (2nd session)	117
> sipping	92
> softwire	73
> speermint	63
> storm	14
> tcpm	33
> tcpm (2nd session)	59
> tictoc	37
> tls	44
> trill	55
> tsvarea (AG)	72
> tsvwg	47
> v6ops	126
> v6ops (second session)	65
> vcarddav	18
> xcon	48
> xmpp2	86
> yam	41
>
>

Regards
Marshall Eubanks
CEO / AmericaFree.TV


From subinoy_das_82@yahoo.com  Thu May 14 23:48:38 2009
Return-Path: <subinoy_das_82@yahoo.com>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 439D43A6936 for <l3vpn@core3.amsl.com>; Thu, 14 May 2009 23:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vu5w1q0T-94s for <l3vpn@core3.amsl.com>; Thu, 14 May 2009 23:48:37 -0700 (PDT)
Received: from n11-vm0.bullet.mail.in.yahoo.com (n11-vm0.bullet.mail.in.yahoo.com [202.86.4.227]) by core3.amsl.com (Postfix) with SMTP id 5A3F83A6A7F for <l3vpn@ietf.org>; Thu, 14 May 2009 23:48:36 -0700 (PDT)
Received: from [202.86.4.170] by n11.bullet.mail.in.yahoo.com with NNFMP; 15 May 2009 06:50:05 -0000
Received: from [203.104.18.48] by t1.bullet.in.yahoo.com with NNFMP; 15 May 2009 06:50:05 -0000
Received: from [127.0.0.1] by omp104.mail.in2.yahoo.com with NNFMP; 15 May 2009 06:50:05 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 908399.73686.bm@omp104.mail.in2.yahoo.com
Received: (qmail 33101 invoked by uid 60001); 15 May 2009 06:50:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1242370202; bh=69M1q55UX4xZrib+MkmNJZo2wWGYASJbIB+Z63onrHg=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=hMFq29BaIbVwd3miIc93DXflGqbzJ7kp3l5m19lgun9TAH1mUW6eIsFYmBl+df66uEMOTAVP6CIXTfvl3M44FkdzLpFaA+eYraFEPp3wWyDGDNVBHGcB9uliHkkHjRTRUT130Y4TyhBQUWFShMEieFOEEM8ZEGt8soYiQVO6BzM=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=q4cEsloCIMzdWKO0mfjORBJQVK2JfkeFKr6YigSGKMzgNAhyU4/DZBgK6JazoApzRDObS24+2nGnkuJPmAxcgI3nMHKr1nXasCeYaAnTfbwg/WFF72C3zkjuPWshr4p4Nu0y0EGgDKwjt2NAT9/5XJ6FX4uj7kKlrqBrh5MOjAU=;
Message-ID: <565693.31903.qm@web94905.mail.in2.yahoo.com>
X-YMail-OSG: fTpMvBEVM1lqclaEwJx4YcmZxUGdSz2f305QqjP275FIIqWLPzS9oUIYZLp8UbeyYlgPvoWpxXt3ZD.tosjBDMlc6.2yYaoE8q4c5qAMGKYcIQaPJAo8Y1QMbc2qogaQzquNuFAEpdM.99J_N1T0C_3rtN.LSMYtyOEhK9Bl5qMv36f5Q39KcykmQt4xlmvdp95hOd_AIRwbyoAMY3tNGcxkJGbRAMZrMAwRIVlxgMIb2_pHKr07UCkQbkeUBioc2xE_Otw-
Received: from [121.242.14.67] by web94905.mail.in2.yahoo.com via HTTP; Fri, 15 May 2009 12:20:02 IST
X-Mailer: YahooMailRC/1277.43 YahooMailWebService/0.7.289.10
Date: Fri, 15 May 2009 12:20:02 +0530 (IST)
From: Subinoy Das <subinoy_das_82@yahoo.com>
Subject: 2 Extended Community introduced in draft-ietf-l3vpn-2547bis-mcast-bgp-05.txt
To: L3VPN MAIL <l3vpn@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-805966418-1242370202=:31903"
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 May 2009 06:48:38 -0000

--0-805966418-1242370202=:31903
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi,=0A=0AIn draft-ietf-l3vpn-2547bis-mcast-bgp-05.txt=0A=0Ain section 6. So=
urce AS Extended Community=0A=0AIf for a given MVPN BGP is used for exchang=
ing C-multicast routes, or=0Aif segmented inter-AS tunnels are used, then w=
hen a PE that has sites=0Aof that MVPN connected to it originates a (unicas=
t) route to VPN-IP=0Aaddresses, the PE MUST include in the BGP Update messa=
ge that carries=0Athis route the Source AS extended community.=0A=0Ain sect=
ion 7. VRF Route Import Extended Community=0A=0ATo support MVPN, in additio=
n to the import/export Route Target(s)=0Aextended communities used by the u=
nicast routing, each VRF on a PE=0AMUST have an import Route Target extende=
d community. We refer to=0Athis Route Target as the "C-multicast Import RT"=
, as this Route=0ATarget controls imports of C-multicast routes into a part=
icular VRF.=0A=0Ain section 11.1.3. Constructing the rest of the C-multicas=
t route=0A=0AFrom the selected UMH route the local PE extracts (a) the auto=
nomous=0Asystem number of the upstream PE (as carried in the Source AS=0Aex=
tended community of the route), and (b) the C-multicast Import RT=0Aof the =
VRF on the upstream PE (the value of this C-multicast Import=0ART is the va=
lue of the VRF Route Import Extended Community carried by=0Athe route). The=
 Source AS field in the C-multicast route is set to=0Athat autonomous syste=
m. The Route Target Extended Community of the Cmulticast=0Aroute is set to =
that C-multicast Import RT.=0A=0AFrom these I understood that to support dr=
aft-ietf-l3vpn-2547bis-mcast-bgp-05.txt, 2 additional Extended Community At=
tributes "VRF Route Import Extended Community" and "Source AS Extended Comm=
unity" are to be sent with VPN-IP update message.=0AMCAST-VPN update messag=
e does not carry these 2 Extended Communities.=0A=0APlease let me know if m=
y understandings are correct or not.=0A=0ARegards,=0ASubinoy=0A=0A=0A=0A   =
   From Chandigarh to Chennai - find friends all over India. Go to http://i=
n.promos.yahoo.com/groups/citygroups/
--0-805966418-1242370202=:31903
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman,new york,times,serif;fon=
t-size:12pt"><div>Hi,<br><br>In draft-ietf-l3vpn-2547bis-mcast-bgp-05.txt<b=
r><br>in section 6. Source AS Extended Community<br><br>If for a given MVPN=
 BGP is used for exchanging C-multicast routes, or<br>if segmented inter-AS=
 tunnels are used, then when a PE that has sites<br>of that MVPN connected =
to it originates a (unicast) route to VPN-IP<br>addresses, the PE MUST incl=
ude in the BGP Update message that carries<br>this route the Source AS exte=
nded community.<br><br>in section 7. VRF Route Import Extended Community<br=
><br>To support MVPN, in addition to the import/export Route Target(s)<br>e=
xtended communities used by the unicast routing, each VRF on a PE<br>MUST h=
ave an import Route Target extended community. We refer to<br>this Route Ta=
rget as the "C-multicast Import RT", as this Route<br>Target controls
 imports of C-multicast routes into a particular VRF.<br><br>in section 11.=
1.3. Constructing the rest of the C-multicast route<br><br>From the selecte=
d UMH route the local PE extracts (a) the autonomous<br>system number of th=
e upstream PE (as carried in the Source AS<br>extended community of the rou=
te), and (b) the C-multicast Import RT<br>of the VRF on the upstream PE (th=
e value of this C-multicast Import<br>RT is the value of the VRF Route Impo=
rt Extended Community carried by<br>the route). The Source AS field in the =
C-multicast route is set to<br>that autonomous system. The Route Target Ext=
ended Community of the Cmulticast<br>route is set to that C-multicast Impor=
t RT.<br><br><span style=3D"font-weight: bold;">From these I understood tha=
t to support draft-ietf-l3vpn-2547bis-mcast-bgp-05.txt, 2 additional Extend=
ed Community Attributes "VRF Route Import Extended Community" and "Source A=
S Extended Community" are to be sent with VPN-IP update
 message.</span><br style=3D"font-weight: bold;"><span style=3D"font-weight=
: bold;">MCAST-VPN update message does not carry these 2 Extended Communiti=
es.</span><br><br>Please let me know if my understandings are correct or no=
t.<br><br>Regards,<br>Subinoy<br></div></div><br>=0A      <!--8--><hr size=
=3D1></hr> Share files, take polls, and make new friends - all under one ro=
of. <a href=3D"http://in.rd.yahoo.com/tagline_groups_8/*http://in.promos.ya=
hoo.com/groups/"> Click here.</a></body></html>
--0-805966418-1242370202=:31903--


From yakov@juniper.net  Fri May 15 08:41:45 2009
Return-Path: <yakov@juniper.net>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B21F3A6889 for <l3vpn@core3.amsl.com>; Fri, 15 May 2009 08:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.418
X-Spam-Level: 
X-Spam-Status: No, score=-6.418 tagged_above=-999 required=5 tests=[AWL=0.180,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n59IUKLKTIgx for <l3vpn@core3.amsl.com>; Fri, 15 May 2009 08:41:44 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id 98E273A70D3 for <l3vpn@ietf.org>; Fri, 15 May 2009 08:41:29 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKSg2NhwoQI/vJi1186ydicHGgR6FwscKG@postini.com; Fri, 15 May 2009 08:43:03 PDT
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.340.0; Fri, 15 May 2009 08:35:35 -0700
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 15 May 2009 08:35:35 -0700
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 15 May 2009 08:35:35 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Fri, 15 May 2009 08:35:34 -0700
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n4FFZYL27598; Fri, 15 May 2009 08:35:34 -0700 (PDT)	(envelope-from yakov@juniper.net)
Message-ID: <200905151535.n4FFZYL27598@magenta.juniper.net>
To: Subinoy Das <subinoy_das_82@yahoo.com>
Subject: Re: 2 Extended Community introduced in draft-ietf-l3vpn-2547bis-mcast-bgp-05.txt 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9213.1242401734.1@juniper.net>
Date: Fri, 15 May 2009 08:35:34 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 15 May 2009 15:35:34.0164 (UTC) FILETIME=[C9936D40:01C9D572]
Cc: L3VPN MAIL <l3vpn@ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 May 2009 15:41:45 -0000

Subinoy,

> Hi,
> 
> In draft-ietf-l3vpn-2547bis-mcast-bgp-05.txt
> 
> in section 6. Source AS Extended Community
> 
> If for a given MVPN BGP is used for exchanging C-multicast routes,
> or if segmented inter-AS tunnels are used, then when a PE that has
> sites of that MVPN connected to it originates a (unicast) route to
> VPN-IP addresses, the PE MUST include in the BGP Update message
> that carries this route the Source AS extended community.
> 
> in section 7. VRF Route Import Extended Community
> 
> To support MVPN, in addition to the import/export Route Target(s)
> extended communities used by the unicast routing, each VRF on a PE
> MUST have an import Route Target extended community. We refer to
> this Route Target as the "C-multicast Import RT", as this Route
> Target controls imports of C-multicast routes into a particular
> VRF.
> 
> in section 11.1.3. Constructing the rest of the C-multicast route
> 
> From the selected UMH route the local PE extracts (a) the autonomous
> system number of the upstream PE (as carried in the Source AS
> extended community of the route), and (b) the C-multicast Import
> RT of the VRF on the upstream PE (the value of this C-multicast
> Import RT is the value of the VRF Route Import Extended Community
> carried by the route). The Source AS field in the C-multicast route
> is set to that autonomous system. The Route Target Extended Community
> of the Cmulticast route is set to that C-multicast Import RT.
> 
> From these I understood that to support
> draft-ietf-l3vpn-2547bis-mcast-bgp-05.txt, 2 additional Extended
> Community Attributes "VRF Route Import Extended Community" and
> "Source AS Extended Community" are to be sent with VPN-IP update
> message.  

That is correct.

> MCAST-VPN update message does not carry these 2 Extended
> Communities.

That is correct too. But as stated in 11.1.3, the information carried
in these communities is used to construct C-multicast routes (as
described in the quote above).

Yakov.
