From isis-wg-bounces@ietf.org Mon Nov 07 12:57:19 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZBF9-0001Sh-NA; Mon, 07 Nov 2005 12:57:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZBF8-0001Sc-CX for isis-wg@megatron.ietf.org; Mon, 07 Nov 2005 12:57:18 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25736 for ; Mon, 7 Nov 2005 12:56:52 -0500 (EST) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZBUl-0002xo-Hc for isis-wg@ietf.org; Mon, 07 Nov 2005 13:13:29 -0500 Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 07 Nov 2005 09:57:07 -0800 X-IronPort-AV: i="3.97,301,1125903600"; d="scan'208"; a="227886209:sNHT28437776" Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id jA7HulZF000699; Mon, 7 Nov 2005 09:57:03 -0800 (PST) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 7 Nov 2005 09:57:02 -0800 Received: from [209.52.110.135] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 7 Nov 2005 09:57:02 -0800 User-Agent: Microsoft-Entourage/10.1.6.040913.0 Date: Mon, 07 Nov 2005 11:57:23 -0600 From: David Ward To: , Christian Hopps , David Ward Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 07 Nov 2005 17:57:02.0488 (UTC) FILETIME=[A8322180:01C5E3C4] X-Spam-Score: 1.1 (+) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: 7bit Cc: Subject: [Isis-wg] ISIS WG meeting agenda at IETF 64 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org All - The meeting this IETF (64) we will have a short agenda: 0) Doc status - 5 mins -: Chairs 1) MI-ISIS - 11 mins - : Stefano Previdi 2) Recharter discussions - 15 mins - :At the last WG meeting in Paris, we announced that we have basically finished our existing charter. We open the list for new charter items and would like to open the mic during this meeting. 3) Anything else? Fud for thought on non-charter items we have discussed in the last year(s) and being discussed elsewhere: A) L2 endpoints passed in ISIS B) FRR "extensions" (many are being discussed in RTGWG) C) V6 TE D) Tunnel concentrator discovery (being discussed in other routing protocol WGs) Or E) Go to sleep until more comes along Thanks DWard, CHopps _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Mon Nov 07 13:52:12 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZC6G-0006fr-Qf; Mon, 07 Nov 2005 13:52:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZC6F-0006fJ-2h for isis-wg@megatron.ietf.org; Mon, 07 Nov 2005 13:52:11 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28996 for ; Mon, 7 Nov 2005 13:51:42 -0500 (EST) Received: from anthrax.middlebury.edu ([140.233.2.72]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZCLq-0004XU-Hu for isis-wg@ietf.org; Mon, 07 Nov 2005 14:08:20 -0500 Received: from arcticcat.middlebury.edu [140.233.2.8] by anthrax.middlebury.edu with XWall v3.35 ; Mon, 7 Nov 2005 13:51:41 -0500 Received: from GRASSHOPPER.middlebury.edu ([140.233.2.6]) by arcticcat.middlebury.edu with Microsoft SMTPSVC(5.0.2195.6713); Mon, 7 Nov 2005 13:50:18 -0500 Received: GRASSHOPPER 140.233.2.6 from 140.233.20.190 140.233.20.190 via HTTP with MS-WebStorage 6.0.6249 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Mon, 07 Nov 2005 13:50:17 -0500 From: "Parker, Jeff" To: ruanlx Message-ID: Thread-Topic: Some question about draft-ietf-isis-wg-mib-24 Thread-Index: AcXjzBhFVop0fk+/EdqiFgANk6/xHg== In-Reply-To: <436F0142.0000B9.06910@bjapp15> Mime-version: 1.0 X-OriginalArrivalTime: 07 Nov 2005 18:50:18.0312 (UTC) FILETIME=[190E2C80:01C5E3CC] X-Spam-Score: 0.8 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: ISIS WG Subject: [Isis-wg] Re: Some question about draft-ietf-isis-wg-mib-24 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1244841492==" Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============1244841492== Content-type: multipart/alternative; boundary="B_3214216217_477592" > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3214216217_477592 Content-type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable On 11/7/05 2:24 AM, "ruanlx" wrote: > hi >=20 > I have some question when implement the draft-ietf-isis-wg-mib-24.txt = . > 1. How can I support multi instances on one router in isis mib ? > 2. How can I support vrf in isis mib ? > 3. Why we can let user to set isisCircExtendedCircID ? > 4. How can I support isisSummAddrEntry level attribute ? >=20 > Thanks for your help^_^. I am sorry for my poor English here. >=20 > Lixiang Ruan > =20 1. You are a few years too late for multi instances. That was supported in the MIB once, but now is not. 2. You may not be able to manage every knob with the standard MIB 3. I=B9m not sure the user wants or needs to set isisCircExtenddCircID. This is probably done via a simple algorithm. 4. This table is used to summarize L1 into L2, so the levels are implicit. - jeff parker --B_3214216217_477592 Content-type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Re: Some question about draft-ietf-isis-wg-mib-24 On 11= /7/05 2:24 AM, "ruanlx" <ruanlx@tom.com> wrote:

hi

   I have some question when implement the draft-ietf-isis-w= g-mib-24.txt  .
   1. How can I support multi instances on one router in isi= s mib ?
   2. How can I support vrf in isis mib ?
   3. Why we can let user to set isisCircExtendedCircID ?    4. How can I support isisSummAddrEntry level attribute ?<= BR>
  Thanks for your help^_^. I am sorry for my poor English here.
Lixiang Ruan
 
  1. <= SPAN STYLE=3D'font-size:12.0px'>You are a few years too late for multi instanc= es.  That was supported in the MIB once, but now is not.
  2. You may not be able to manage every knob with the standard MIB
  3. I’m not sure the user wants or needs to set isisCircExten= ddCircID.  This is probably done via a simple algorithm.=20
  4. This table is used to summarize L1 into L2, so the levels are i= mplicit.  

- jeff parker --B_3214216217_477592-- --===============1244841492== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --===============1244841492==-- From isis-wg-bounces@ietf.org Tue Nov 08 13:59:09 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZYgX-0006c3-R4; Tue, 08 Nov 2005 13:59:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZYgW-0006bw-7N for isis-wg@megatron.ietf.org; Tue, 08 Nov 2005 13:59:08 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25865 for ; Tue, 8 Nov 2005 13:58:41 -0500 (EST) Received: from smtpout1.bayarea.net ([209.128.95.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZYwM-0004r1-EJ for isis-wg@ietf.org; Tue, 08 Nov 2005 14:15:31 -0500 Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id jA8Ix2CO013032; Tue, 8 Nov 2005 10:59:02 -0800 Received: from shell4.bayarea.net (localhost [127.0.0.1]) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id jA8IwsBX004625; Tue, 8 Nov 2005 10:58:54 -0800 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id jA8Iwr0Y004619; Tue, 8 Nov 2005 10:58:54 -0800 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Tue, 8 Nov 2005 10:58:53 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: ruanlx Subject: Re: [Isis-wg] Re: Some question about draft-ietf-isis-wg-mib-24 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: ISIS WG X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org On Mon, 7 Nov 2005, Parker, Jeff wrote: > On 11/7/05 2:24 AM, "ruanlx" wrote: ... > > 1. How can I support multi instances on one router in isis mib ? ... > 1. You are a few years too late for multi instances. That was > supported in the MIB once, but now is not. This can be done by means of separate contexts (SNMPv3) or separate community names (SNMv1/SNMPv2c). //cmh _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Nov 09 22:27:20 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ea35s-0001QM-9c; Wed, 09 Nov 2005 22:27:20 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ea35q-0001Pj-QA for isis-wg@megatron.ietf.org; Wed, 09 Nov 2005 22:27:19 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01458 for ; Wed, 9 Nov 2005 22:26:50 -0500 (EST) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ea3Ly-0003ap-Fl for isis-wg@ietf.org; Wed, 09 Nov 2005 22:43:59 -0500 Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 09 Nov 2005 19:27:08 -0800 X-IronPort-AV: i="3.97,311,1125903600"; d="scan'208"; a="228778775:sNHT24934240" Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id jAA3QnZn012206; Wed, 9 Nov 2005 19:26:58 -0800 (PST) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 9 Nov 2005 19:27:02 -0800 Received: from [209.52.110.135] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 9 Nov 2005 19:27:01 -0800 User-Agent: Microsoft-Entourage/10.1.6.040913.0 Date: Wed, 09 Nov 2005 21:26:58 -0600 From: David Ward To: , David Ward , Christian Hopps Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 10 Nov 2005 03:27:01.0744 (UTC) FILETIME=[9D5DF700:01C5E5A6] X-Spam-Score: 1.1 (+) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Content-Transfer-Encoding: 7bit Cc: Subject: [Isis-wg] ISIS WG IETF 64 (Vancouver) Notes X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Folks, Please review and comment for correctness. The deadline for comments is Nov 18, 2005 ------------- ISIS IETF 64 Chairs: Chris Hopps, David Ward Scribe: David Ward Doc Status Cap - advert .... Alex to send comments to authors Link attr - new draft right after mtg based on AD comments V6 TE to go PS (normative V6 and V4 TE and GMPLS) GMPLS to be bis'ed as PS - Kireeti to complete immediately ----------------------------------- Previdi - MI-ISIS ???: What is the application of this? Previdi: To solve share fate problem of control over same physical topology. Segment the control plane for each service to different instances. ----------------------------------- Rechartering WG voted to put itself to sleep. Dissenting votes. We will send out a proposed charter that includes MI ISIS L2 in ISIS Tunnel Concentrator Discovery IPFRR extensions will be tracked but no deliverables until brought forth by RTGWG _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Nov 10 14:16:49 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaHuj-0001kT-NV; Thu, 10 Nov 2005 14:16:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaHuh-0001kO-TU for isis-wg@megatron.ietf.org; Thu, 10 Nov 2005 14:16:48 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27833 for ; Thu, 10 Nov 2005 14:16:20 -0500 (EST) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EaIAy-0004jL-QN for isis-wg@ietf.org; Thu, 10 Nov 2005 14:33:37 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 10 Nov 2005 11:16:38 -0800 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jAAJG4ZY004552; Thu, 10 Nov 2005 11:16:34 -0800 (PST) Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 10 Nov 2005 11:16:29 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Isis-wg] ISIS WG IETF 64 (Vancouver) Notes Date: Thu, 10 Nov 2005 11:16:28 -0800 Message-ID: Thread-Topic: [Isis-wg] ISIS WG IETF 64 (Vancouver) Notes Thread-Index: AcXlpwIKDjojGvBRSUa3jidyDMPfigAg1sNA From: "Les Ginsberg \(ginsberg\)" To: "David Ward" , , "Christian Hopps" X-OriginalArrivalTime: 10 Nov 2005 19:16:29.0263 (UTC) FILETIME=[40A785F0:01C5E62B] X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org > -----Original Message----- > From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On Behalf > Of David Ward > Sent: Wednesday, November 09, 2005 7:27 PM > To: isis-wg@ietf.org; David Ward; Christian Hopps > Subject: [Isis-wg] ISIS WG IETF 64 (Vancouver) Notes >=20 > Folks, >=20 > Please review and comment for correctness. The deadline for > comments is Nov 18, 2005 >=20 >=20 >=20 >=20 > ------------- > ISIS IETF 64 >=20 > Chairs: Chris Hopps, David Ward >=20 > Scribe: David Ward >=20 >=20 > Doc Status >=20 > Cap - advert .... Alex to send comments to authors >=20 > Link attr - new draft right after mtg based on AD comments >=20 > V6 TE to go PS (normative V6 and V4 TE and GMPLS) >=20 > GMPLS to be bis'ed as PS - Kireeti to complete immediately >=20 > ----------------------------------- >=20 > Previdi - MI-ISIS >=20 > ???: What is the application of this? >=20 > Previdi: To solve share fate problem of control over same physical > topology. > Segment the control plane for each service to different instances. >=20 >=20 > ----------------------------------- >=20 > Rechartering >=20 > WG voted to put itself to sleep. Ummm...is that what we did??? My recollection is that the chair phrased the question as a double negative - which caused a good deal of quizzical looking around as if to say "Which way are we being asked to vote??". In any case, it seems that there is still some work to do, however modest. I don't see that it makes sense to start hibernating before that work is done. Surely we can all catch cat naps while the work load remains light, and then have a well deserved deep sleep when winter actually arrives. I presume that is the intent of the new charter below - so maybe my light rant here is just to get confirmation that the statement above isn't really being used to set the immediate future of the WG. Les > Dissenting votes. >=20 >=20 >=20 > We will send out a proposed charter that includes >=20 > MI ISIS > L2 in ISIS > Tunnel Concentrator Discovery >=20 > IPFRR extensions will be tracked but no deliverables until brought forth > by > RTGWG >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Nov 10 14:39:53 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaIB1-0008CM-GC; Thu, 10 Nov 2005 14:33:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaIAz-0008Ae-MK for isis-wg@megatron.ietf.org; Thu, 10 Nov 2005 14:33:37 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28385 for ; Thu, 10 Nov 2005 14:33:09 -0500 (EST) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EaIGK-00051e-U4 for isis-wg@ietf.org; Thu, 10 Nov 2005 14:39:09 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 10 Nov 2005 11:22:10 -0800 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jAAJLeZa008320; Thu, 10 Nov 2005 11:22:08 -0800 (PST) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 10 Nov 2005 11:22:05 -0800 Received: from [209.52.110.135] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 10 Nov 2005 11:22:04 -0800 User-Agent: Microsoft-Entourage/10.1.6.040913.0 Date: Thu, 10 Nov 2005 13:22:03 -0600 Subject: Re: [Isis-wg] ISIS WG IETF 64 (Vancouver) Notes From: David Ward To: "Les Ginsberg (ginsberg)" , , Christian Hopps , David Ward Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 10 Nov 2005 19:22:04.0977 (UTC) FILETIME=[08C16A10:01C5E62C] X-Spam-Score: 1.1 (+) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 Content-Transfer-Encoding: 7bit Cc: X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Les - To clarify: We voted (stated) There was dissent (stated) We will propose charter w/ below items (stated) Notes to be posted will more clearly reflect this. Thanks -DWard On 11/10/05 1:16 PM, "Les Ginsberg (ginsberg)" wrote: > > >> -----Original Message----- >> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On > Behalf >> Of David Ward >> Sent: Wednesday, November 09, 2005 7:27 PM >> To: isis-wg@ietf.org; David Ward; Christian Hopps >> Subject: [Isis-wg] ISIS WG IETF 64 (Vancouver) Notes >> >> Folks, >> >> Please review and comment for correctness. The deadline for >> comments is Nov 18, 2005 >> >> >> >> >> ------------- >> ISIS IETF 64 >> >> Chairs: Chris Hopps, David Ward >> >> Scribe: David Ward >> >> >> Doc Status >> >> Cap - advert .... Alex to send comments to authors >> >> Link attr - new draft right after mtg based on AD comments >> >> V6 TE to go PS (normative V6 and V4 TE and GMPLS) >> >> GMPLS to be bis'ed as PS - Kireeti to complete immediately >> >> ----------------------------------- >> >> Previdi - MI-ISIS >> >> ???: What is the application of this? >> >> Previdi: To solve share fate problem of control over same physical >> topology. >> Segment the control plane for each service to different instances. >> >> >> ----------------------------------- >> >> Rechartering >> >> WG voted to put itself to sleep. > > Ummm...is that what we did??? > My recollection is that the chair phrased the question as a double > negative - which caused a good deal of quizzical looking around as if to > say "Which way are we being asked to vote??". > > In any case, it seems that there is still some work to do, however > modest. I don't see that it makes sense to start hibernating before that > work is done. Surely we can all catch cat naps while the work load > remains light, and then have a well deserved deep sleep when winter > actually arrives. > > I presume that is the intent of the new charter below - so maybe my > light rant here is just to get confirmation that the statement above > isn't really being used to set the immediate future of the WG. > > Les > >> Dissenting votes. >> >> >> >> We will send out a proposed charter that includes >> >> MI ISIS >> L2 in ISIS >> Tunnel Concentrator Discovery >> >> IPFRR extensions will be tracked but no deliverables until brought > forth >> by >> RTGWG >> >> >> >> >> >> _______________________________________________ >> Isis-wg mailing list >> Isis-wg@ietf.org >> https://www1.ietf.org/mailman/listinfo/isis-wg > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Nov 16 15:50:26 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EcUEc-0004Dq-IT; Wed, 16 Nov 2005 15:50:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EcUEG-00043O-VQ; Wed, 16 Nov 2005 15:50:04 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23495; Wed, 16 Nov 2005 15:49:32 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EcUVm-0008Vc-Jj; Wed, 16 Nov 2005 16:08:10 -0500 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EcUED-0008T9-DE; Wed, 16 Nov 2005 15:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 16 Nov 2005 15:50:01 -0500 X-Spam-Score: 0.4 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : IPv6 Traffic Engineering in IS-IS Author(s) : J. Harrison, et al. Filename : draft-ietf-isis-ipv6-te-02.txt Pages : 10 Date : 2005-11-16 This document specifies a method for exchanging IPv6 Traffic Engineering information using the IS-IS routing protocol. The described method uses three new TLVs, together with two new sub-TLVs of the Extended IS Reachability TLV. The information distributed allows a CSPF algorithm to calculate traffic engineered routes using IPv6 addresses. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-te-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-isis-ipv6-te-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-isis-ipv6-te-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-11-16150552.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-ipv6-te-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-ipv6-te-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-11-16150552.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Tue Nov 22 10:51:13 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EeaQL-0003pD-SB; Tue, 22 Nov 2005 10:51:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EeaQK-0003nB-4c for isis-wg@megatron.ietf.org; Tue, 22 Nov 2005 10:51:12 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02799 for ; Tue, 22 Nov 2005 10:50:34 -0500 (EST) Received: from kremlin.juniper.net ([207.17.137.120]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eeaj0-0001r9-JW for isis-wg@ietf.org; Tue, 22 Nov 2005 11:10:30 -0500 Received: from unknown (HELO alpha.jnpr.net) ([172.24.18.126]) by kremlin.juniper.net with ESMTP; 22 Nov 2005 07:50:55 -0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.97,362,1125903600"; d="scan'208"; a="511987300:sNHT24064940" Received: from [172.26.200.121] ([172.26.200.121]) by alpha.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 Nov 2005 07:50:47 -0800 Message-ID: <43833E55.8040700@juniper.net> Date: Tue, 22 Nov 2005 16:50:45 +0100 From: Hannes Gredler User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: jon.harrison@dataconnection.com, jon.berger@dataconnection.com Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 22 Nov 2005 15:50:47.0408 (UTC) FILETIME=[814AE700:01C5EF7C] X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Content-Transfer-Encoding: 7bit Cc: isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org hi jon & jon, i fail to understand the necessity of the IPv6 Global Interface Address TLV - my train of thought is that TE for v4 is working fine without an indication that the neighor is TE capable ... could you pls explain your rationale behind ? /hannes --- 4.5 IPv6 Global Interface Address TLV The IPv6 Global Interface Address TLV is TLV type 233. The TLV structure is identical to that of the IPv6 Interface Address TLV defined in [IPv6], but the semantics are different. In particular, the TLV is included in IIH PDUs for those interfaces using IPv6 TE extensions. The TLV contains global or site-local IPv6 addresses assigned to the interface that is sending the Hello. The IPv6 Global Interface Address TLV is not used in LSPs. --- Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. > > Title : IPv6 Traffic Engineering in IS-IS > Author(s) : J. Harrison, et al. > Filename : draft-ietf-isis-ipv6-te-02.txt > Pages : 10 > Date : 2005-11-16 > > This document specifies a method for exchanging IPv6 Traffic > Engineering information using the IS-IS routing protocol. The > described method uses three new TLVs, together with two new sub-TLVs > of the Extended IS Reachability TLV. The information distributed > allows a CSPF algorithm to calculate traffic engineered routes using > IPv6 addresses. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-te-02.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > > Internet-Drafts are also available by anonymous FTP. Login with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-isis-ipv6-te-02.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-isis-ipv6-te-02.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Nov 23 03:57:54 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EeqRu-0005Xv-Kw; Wed, 23 Nov 2005 03:57:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EeqRt-0005WU-96 for isis-wg@megatron.ietf.org; Wed, 23 Nov 2005 03:57:53 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29638 for ; Wed, 23 Nov 2005 03:57:13 -0500 (EST) Received: from kremlin.juniper.net ([207.17.137.120]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eeqkg-0002lN-G3 for isis-wg@ietf.org; Wed, 23 Nov 2005 04:17:20 -0500 Received: from unknown (HELO beta.jnpr.net) ([172.24.18.109]) by kremlin.juniper.net with ESMTP; 23 Nov 2005 00:57:40 -0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.97,364,1125903600"; d="scan'208"; a="512106907:sNHT24093644" Received: from [172.26.200.121] ([172.26.200.121]) by beta.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Nov 2005 00:57:39 -0800 Message-ID: <43842F01.80101@juniper.net> Date: Wed, 23 Nov 2005 09:57:37 +0100 From: Hannes Gredler User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jonathan Harrison Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt References: <8E4A9A66F7AED54C89F478AF4477C7D8445443@enfimail1.datcon.co.uk> In-Reply-To: <8E4A9A66F7AED54C89F478AF4477C7D8445443@enfimail1.datcon.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Nov 2005 08:57:39.0976 (UTC) FILETIME=[F53EB080:01C5F00B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d Content-Transfer-Encoding: 7bit Cc: Jon Berger , isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org jon, understood - a question: for TE we only need to uniquely identify a given link, right ? - i am wondering if the EUI64 part of the link-local adress would be enough to unambigously identify a V6 TE link. /hannes Jonathan Harrison wrote: > Hannes, > > The reason this TLV is required is alluded to in section 3.2.3 of the draft. It essentially comes down to the fact that IPv6 has link-local and global addresses, whereas IPv4 does not. > > The non-TE IPv6 TLVs only provide link-local IPv6 addresses on IIH messages. This is fine for standard IP forwarding, as the address is only used locally as the next hop address for forwarding to the peer. > > When a node builds the Extended IS Reachability TLV, it may include the local and remote IPv6 addresses for the connection to the peer (in the IPv6 Interface Address sub-TLV and IPv6 Neighbor Address sub-TLV). These IPv6 addresses are visible to remote nodes, and therefore cannot be link-local addresses. > > So if a node is going to build a useful Extended IS Reachability TLV, it needs more than just an IPv6 link-local address from the neighbor - it needs an IPv6 global address too. The IPv6 Global Interface Address TLV provides a mechanism for getting hold of this information from received IIH messages. > > I hope this clarifies things. > > Thanks, > Jon > > > > -----Original Message----- > From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org]On > Behalf Of Hannes Gredler > Sent: 22 November 2005 15:51 > To: Jonathan Harrison; Jon Berger > Cc: isis-wg@ietf.org > Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt > > > hi jon & jon, > > i fail to understand the necessity of the > IPv6 Global Interface Address TLV - > > my train of thought is that TE for v4 is working > fine without an indication that the neighor > is TE capable ... > > could you pls explain your rationale behind ? > > /hannes > > --- > > 4.5 IPv6 Global Interface Address TLV > > The IPv6 Global Interface Address TLV is TLV type 233. The TLV > structure is identical to that of the IPv6 Interface Address TLV > defined in [IPv6], but the semantics are different. In particular, > the TLV is included in IIH PDUs for those interfaces using IPv6 TE > extensions. The TLV contains global or site-local IPv6 addresses > assigned to the interface that is sending the Hello. > > The IPv6 Global Interface Address TLV is not used in LSPs. > > --- > > Internet-Drafts@ietf.org wrote: > >>A New Internet-Draft is available from the on-line Internet-Drafts directories. >>This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. >> >> Title : IPv6 Traffic Engineering in IS-IS >> Author(s) : J. Harrison, et al. >> Filename : draft-ietf-isis-ipv6-te-02.txt >> Pages : 10 >> Date : 2005-11-16 >> >>This document specifies a method for exchanging IPv6 Traffic >> Engineering information using the IS-IS routing protocol. The >> described method uses three new TLVs, together with two new sub-TLVs >> of the Extended IS Reachability TLV. The information distributed >> allows a CSPF algorithm to calculate traffic engineered routes using >> IPv6 addresses. >> >>A URL for this Internet-Draft is: >>http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-te-02.txt >> >>To remove yourself from the I-D Announcement list, send a message to >>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. >>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce >>to change your subscription settings. >> >> >>Internet-Drafts are also available by anonymous FTP. Login with the username >>"anonymous" and a password of your e-mail address. After logging in, >>type "cd internet-drafts" and then >> "get draft-ietf-isis-ipv6-te-02.txt". >> >>A list of Internet-Drafts directories can be found in >>http://www.ietf.org/shadow.html >>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >> >> >>Internet-Drafts can also be obtained by e-mail. >> >>Send a message to: >> mailserv@ietf.org. >>In the body type: >> "FILE /internet-drafts/draft-ietf-isis-ipv6-te-02.txt". >> >>NOTE: The mail server at ietf.org can return the document in >> MIME-encoded form by using the "mpack" utility. To use this >> feature, insert the command "ENCODING mime" before the "FILE" >> command. To decode the response(s), you will need "munpack" or >> a MIME-compliant mail reader. Different MIME-compliant mail readers >> exhibit different behavior, especially when dealing with >> "multipart" MIME messages (i.e. documents which have been split >> up into multiple messages), so check your local documentation on >> how to manipulate these messages. >> >> >>Below is the data which will enable a MIME compliant mail reader >>implementation to automatically retrieve the ASCII version of the >>Internet-Draft. >> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>Isis-wg mailing list >>Isis-wg@ietf.org >>https://www1.ietf.org/mailman/listinfo/isis-wg > > > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Nov 23 08:06:55 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EeuKt-0007tB-Sf; Wed, 23 Nov 2005 08:06:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EeuKt-0007t6-8K for isis-wg@megatron.ietf.org; Wed, 23 Nov 2005 08:06:55 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26830 for ; Wed, 23 Nov 2005 08:06:15 -0500 (EST) Received: from smtp2.dataconnection.com ([192.91.191.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eeudj-000846-HA for isis-wg@ietf.org; Wed, 23 Nov 2005 08:26:25 -0500 Received: from enfimail1.datcon.co.uk ([172.19.14.253]) by smtp2.dataconnection.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Nov 2005 13:06:39 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: RE: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt Date: Wed, 23 Nov 2005 13:06:39 -0000 Message-ID: <8E4A9A66F7AED54C89F478AF4477C7D8445448@enfimail1.datcon.co.uk> Thread-Topic: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt Thread-Index: AcXwC/b2oknntGtSQiqISliEDAX+8wAEh+8g From: "Jonathan Harrison" To: "Hannes Gredler" X-OriginalArrivalTime: 23 Nov 2005 13:06:39.0947 (UTC) FILETIME=[BE2959B0:01C5F02E] X-Spam-Score: 0.0 (/) X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44 Content-Transfer-Encoding: quoted-printable Cc: Jon Berger , isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Hannes, The main advantage of using the local/remote global IPv6 addresses is = that it allows a remote node to specify them in an ERO after performing = a CSPF calculation. In addition, the interface identifier part of a link-local address is = only guaranteed to be unique on that subnet. While it is likely to be a = unique EUI-64 address, this is not mandated by RFC 3513. Jon -----Original Message----- From: Hannes Gredler [mailto:hannes@juniper.net] Sent: 23 November 2005 08:58 To: Jonathan Harrison Cc: isis-wg@ietf.org; Jon Berger Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt jon, understood - a question: for TE we only need to uniquely identify a given link, right ? - i am wondering if the EUI64 part of the link-local adress would be enough to unambigously identify a V6 TE link. /hannes Jonathan Harrison wrote: > Hannes, >=20 > The reason this TLV is required is alluded to in section 3.2.3 of the = draft. It essentially comes down to the fact that IPv6 has link-local = and global addresses, whereas IPv4 does not. >=20 > The non-TE IPv6 TLVs only provide link-local IPv6 addresses on IIH = messages. This is fine for standard IP forwarding, as the address is = only used locally as the next hop address for forwarding to the peer. >=20 > When a node builds the Extended IS Reachability TLV, it may include = the local and remote IPv6 addresses for the connection to the peer (in = the IPv6 Interface Address sub-TLV and IPv6 Neighbor Address sub-TLV). = These IPv6 addresses are visible to remote nodes, and therefore cannot = be link-local addresses. >=20 > So if a node is going to build a useful Extended IS Reachability TLV, = it needs more than just an IPv6 link-local address from the neighbor - = it needs an IPv6 global address too. The IPv6 Global Interface Address = TLV provides a mechanism for getting hold of this information from = received IIH messages. >=20 > I hope this clarifies things. >=20 > Thanks, > Jon >=20 >=20 >=20 > -----Original Message----- > From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org]On > Behalf Of Hannes Gredler > Sent: 22 November 2005 15:51 > To: Jonathan Harrison; Jon Berger > Cc: isis-wg@ietf.org > Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt >=20 >=20 > hi jon & jon, >=20 > i fail to understand the necessity of the > IPv6 Global Interface Address TLV - >=20 > my train of thought is that TE for v4 is working > fine without an indication that the neighor > is TE capable ... >=20 > could you pls explain your rationale behind ? >=20 > /hannes >=20 > --- >=20 > 4.5 IPv6 Global Interface Address TLV >=20 > The IPv6 Global Interface Address TLV is TLV type 233. The TLV > structure is identical to that of the IPv6 Interface Address TLV > defined in [IPv6], but the semantics are different. In = particular, > the TLV is included in IIH PDUs for those interfaces using IPv6 TE > extensions. The TLV contains global or site-local IPv6 addresses > assigned to the interface that is sending the Hello. >=20 > The IPv6 Global Interface Address TLV is not used in LSPs. >=20 > --- >=20 > Internet-Drafts@ietf.org wrote: >=20 >>A New Internet-Draft is available from the on-line Internet-Drafts = directories. >>This draft is a work item of the IS-IS for IP Internets Working Group = of the IETF. >> >> Title : IPv6 Traffic Engineering in IS-IS >> Author(s) : J. Harrison, et al. >> Filename : draft-ietf-isis-ipv6-te-02.txt >> Pages : 10 >> Date : 2005-11-16 >>=09 >>This document specifies a method for exchanging IPv6 Traffic >> Engineering information using the IS-IS routing protocol. The >> described method uses three new TLVs, together with two new = sub-TLVs >> of the Extended IS Reachability TLV. The information distributed >> allows a CSPF algorithm to calculate traffic engineered routes = using >> IPv6 addresses. >> >>A URL for this Internet-Draft is: >>http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-te-02.txt >> >>To remove yourself from the I-D Announcement list, send a message to=20 >>i-d-announce-request@ietf.org with the word unsubscribe in the body of = the message. =20 >>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce = >>to change your subscription settings. >> >> >>Internet-Drafts are also available by anonymous FTP. Login with the = username >>"anonymous" and a password of your e-mail address. After logging in, >>type "cd internet-drafts" and then >> "get draft-ietf-isis-ipv6-te-02.txt". >> >>A list of Internet-Drafts directories can be found in >>http://www.ietf.org/shadow.html=20 >>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >> >> >>Internet-Drafts can also be obtained by e-mail. >> >>Send a message to: >> mailserv@ietf.org. >>In the body type: >> "FILE /internet-drafts/draft-ietf-isis-ipv6-te-02.txt". >>=09 >>NOTE: The mail server at ietf.org can return the document in >> MIME-encoded form by using the "mpack" utility. To use this >> feature, insert the command "ENCODING mime" before the "FILE" >> command. To decode the response(s), you will need "munpack" or >> a MIME-compliant mail reader. Different MIME-compliant mail readers >> exhibit different behavior, especially when dealing with >> "multipart" MIME messages (i.e. documents which have been split >> up into multiple messages), so check your local documentation on >> how to manipulate these messages. >> =09 >> =09 >>Below is the data which will enable a MIME compliant mail reader >>implementation to automatically retrieve the ASCII version of the >>Internet-Draft. >> >> >>-----------------------------------------------------------------------= - >> >>_______________________________________________ >>Isis-wg mailing list >>Isis-wg@ietf.org >>https://www1.ietf.org/mailman/listinfo/isis-wg >=20 >=20 > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Nov 23 10:12:50 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EewIk-00018h-6F; Wed, 23 Nov 2005 10:12:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eeas9-0008NT-Di for isis-wg@megatron.ietf.org; Tue, 22 Nov 2005 11:19:57 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07095 for ; Tue, 22 Nov 2005 11:19:19 -0500 (EST) Received: from smtp2.dataconnection.com ([192.91.191.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EebAp-0003le-Od for isis-wg@ietf.org; Tue, 22 Nov 2005 11:39:16 -0500 Received: from enfimail1.datcon.co.uk ([172.19.14.253]) by smtp2.dataconnection.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 Nov 2005 16:19:47 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: RE: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt Date: Tue, 22 Nov 2005 16:19:47 -0000 Message-ID: <8E4A9A66F7AED54C89F478AF4477C7D8445443@enfimail1.datcon.co.uk> Thread-Topic: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt Thread-Index: AcXvfMRFJ383l3XgQQ+K+1YytQHV9AAAIKyQ From: "Jonathan Harrison" To: "Hannes Gredler" X-OriginalArrivalTime: 22 Nov 2005 16:19:47.0527 (UTC) FILETIME=[8E7BFD70:01C5EF80] X-Spam-Score: 0.0 (/) X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 23 Nov 2005 10:12:48 -0500 Cc: Jon Berger , isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Hannes, The reason this TLV is required is alluded to in section 3.2.3 of the = draft. It essentially comes down to the fact that IPv6 has link-local = and global addresses, whereas IPv4 does not. The non-TE IPv6 TLVs only provide link-local IPv6 addresses on IIH = messages. This is fine for standard IP forwarding, as the address is = only used locally as the next hop address for forwarding to the peer. When a node builds the Extended IS Reachability TLV, it may include the = local and remote IPv6 addresses for the connection to the peer (in the = IPv6 Interface Address sub-TLV and IPv6 Neighbor Address sub-TLV). = These IPv6 addresses are visible to remote nodes, and therefore cannot = be link-local addresses. So if a node is going to build a useful Extended IS Reachability TLV, it = needs more than just an IPv6 link-local address from the neighbor - it = needs an IPv6 global address too. The IPv6 Global Interface Address TLV = provides a mechanism for getting hold of this information from received = IIH messages. I hope this clarifies things. Thanks, Jon -----Original Message----- From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org]On Behalf Of Hannes Gredler Sent: 22 November 2005 15:51 To: Jonathan Harrison; Jon Berger Cc: isis-wg@ietf.org Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt hi jon & jon, i fail to understand the necessity of the IPv6 Global Interface Address TLV - my train of thought is that TE for v4 is working fine without an indication that the neighor is TE capable ... could you pls explain your rationale behind ? /hannes --- 4.5 IPv6 Global Interface Address TLV The IPv6 Global Interface Address TLV is TLV type 233. The TLV structure is identical to that of the IPv6 Interface Address TLV defined in [IPv6], but the semantics are different. In particular, the TLV is included in IIH PDUs for those interfaces using IPv6 TE extensions. The TLV contains global or site-local IPv6 addresses assigned to the interface that is sending the Hello. The IPv6 Global Interface Address TLV is not used in LSPs. --- Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the IS-IS for IP Internets Working Group = of the IETF. >=20 > Title : IPv6 Traffic Engineering in IS-IS > Author(s) : J. Harrison, et al. > Filename : draft-ietf-isis-ipv6-te-02.txt > Pages : 10 > Date : 2005-11-16 > =09 > This document specifies a method for exchanging IPv6 Traffic > Engineering information using the IS-IS routing protocol. The > described method uses three new TLVs, together with two new = sub-TLVs > of the Extended IS Reachability TLV. The information distributed > allows a CSPF algorithm to calculate traffic engineered routes = using > IPv6 addresses. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-te-02.txt >=20 > To remove yourself from the I-D Announcement list, send a message to=20 > i-d-announce-request@ietf.org with the word unsubscribe in the body of = the message. =20 > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce = > to change your subscription settings. >=20 >=20 > Internet-Drafts are also available by anonymous FTP. Login with the = username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-isis-ipv6-te-02.txt". >=20 > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html=20 > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >=20 >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-isis-ipv6-te-02.txt". > =09 > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > =09 > =09 > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. >=20 >=20 > = ------------------------------------------------------------------------ >=20 > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Nov 23 11:44:00 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eexiy-0005qm-LT; Wed, 23 Nov 2005 11:44:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eexix-0005qd-3a for isis-wg@megatron.ietf.org; Wed, 23 Nov 2005 11:43:59 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24484 for ; Wed, 23 Nov 2005 11:43:18 -0500 (EST) Received: from borg.juniper.net ([207.17.137.119]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eey1q-0004iG-D0 for isis-wg@ietf.org; Wed, 23 Nov 2005 12:03:30 -0500 Received: from unknown (HELO beta.jnpr.net) ([172.24.18.109]) by borg.juniper.net with ESMTP; 23 Nov 2005 08:43:49 -0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.97,364,1125903600"; d="scan'208"; a="512931843:sNHT24461720" Received: from [172.26.200.121] ([172.26.200.121]) by beta.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Nov 2005 08:43:46 -0800 Message-ID: <43849C40.3090807@juniper.net> Date: Wed, 23 Nov 2005 17:43:44 +0100 From: Hannes Gredler User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jonathan Harrison Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt References: <8E4A9A66F7AED54C89F478AF4477C7D8445448@enfimail1.datcon.co.uk> In-Reply-To: <8E4A9A66F7AED54C89F478AF4477C7D8445448@enfimail1.datcon.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Nov 2005 16:43:47.0039 (UTC) FILETIME=[12E9D6F0:01C5F04D] X-Spam-Score: 0.0 (/) X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba Content-Transfer-Encoding: 7bit Cc: Jon Berger , isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org ok tx - makes all sense now; - /hannes Jonathan Harrison wrote: > Hannes, > > The main advantage of using the local/remote global IPv6 addresses is that it allows a remote node to specify them in an ERO after performing a CSPF calculation. > > In addition, the interface identifier part of a link-local address is only guaranteed to be unique on that subnet. While it is likely to be a unique EUI-64 address, this is not mandated by RFC 3513. > > Jon > > > -----Original Message----- > From: Hannes Gredler [mailto:hannes@juniper.net] > Sent: 23 November 2005 08:58 > To: Jonathan Harrison > Cc: isis-wg@ietf.org; Jon Berger > Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt > > > jon, > > understood - a question: > > for TE we only need to uniquely identify a given link, right ? - > i am wondering if the EUI64 part of the link-local adress would be > enough to unambigously identify a V6 TE link. > > /hannes > > Jonathan Harrison wrote: > >>Hannes, >> >>The reason this TLV is required is alluded to in section 3.2.3 of the draft. It essentially comes down to the fact that IPv6 has link-local and global addresses, whereas IPv4 does not. >> >>The non-TE IPv6 TLVs only provide link-local IPv6 addresses on IIH messages. This is fine for standard IP forwarding, as the address is only used locally as the next hop address for forwarding to the peer. >> >>When a node builds the Extended IS Reachability TLV, it may include the local and remote IPv6 addresses for the connection to the peer (in the IPv6 Interface Address sub-TLV and IPv6 Neighbor Address sub-TLV). These IPv6 addresses are visible to remote nodes, and therefore cannot be link-local addresses. >> >>So if a node is going to build a useful Extended IS Reachability TLV, it needs more than just an IPv6 link-local address from the neighbor - it needs an IPv6 global address too. The IPv6 Global Interface Address TLV provides a mechanism for getting hold of this information from received IIH messages. >> >>I hope this clarifies things. >> >>Thanks, >>Jon >> >> >> >>-----Original Message----- >>From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org]On >>Behalf Of Hannes Gredler >>Sent: 22 November 2005 15:51 >>To: Jonathan Harrison; Jon Berger >>Cc: isis-wg@ietf.org >>Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-te-02.txt >> >> >>hi jon & jon, >> >>i fail to understand the necessity of the >>IPv6 Global Interface Address TLV - >> >>my train of thought is that TE for v4 is working >>fine without an indication that the neighor >>is TE capable ... >> >>could you pls explain your rationale behind ? >> >>/hannes >> >>--- >> >>4.5 IPv6 Global Interface Address TLV >> >> The IPv6 Global Interface Address TLV is TLV type 233. The TLV >> structure is identical to that of the IPv6 Interface Address TLV >> defined in [IPv6], but the semantics are different. In particular, >> the TLV is included in IIH PDUs for those interfaces using IPv6 TE >> extensions. The TLV contains global or site-local IPv6 addresses >> assigned to the interface that is sending the Hello. >> >> The IPv6 Global Interface Address TLV is not used in LSPs. >> >>--- >> >>Internet-Drafts@ietf.org wrote: >> >> >>>A New Internet-Draft is available from the on-line Internet-Drafts directories. >>>This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. >>> >>> Title : IPv6 Traffic Engineering in IS-IS >>> Author(s) : J. Harrison, et al. >>> Filename : draft-ietf-isis-ipv6-te-02.txt >>> Pages : 10 >>> Date : 2005-11-16 >>> >>>This document specifies a method for exchanging IPv6 Traffic >>> Engineering information using the IS-IS routing protocol. The >>> described method uses three new TLVs, together with two new sub-TLVs >>> of the Extended IS Reachability TLV. The information distributed >>> allows a CSPF algorithm to calculate traffic engineered routes using >>> IPv6 addresses. >>> >>>A URL for this Internet-Draft is: >>>http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-te-02.txt >>> >>>To remove yourself from the I-D Announcement list, send a message to >>>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. >>>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce >>>to change your subscription settings. >>> >>> >>>Internet-Drafts are also available by anonymous FTP. Login with the username >>>"anonymous" and a password of your e-mail address. After logging in, >>>type "cd internet-drafts" and then >>> "get draft-ietf-isis-ipv6-te-02.txt". >>> >>>A list of Internet-Drafts directories can be found in >>>http://www.ietf.org/shadow.html >>>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >>> >>> >>>Internet-Drafts can also be obtained by e-mail. >>> >>>Send a message to: >>> mailserv@ietf.org. >>>In the body type: >>> "FILE /internet-drafts/draft-ietf-isis-ipv6-te-02.txt". >>> >>>NOTE: The mail server at ietf.org can return the document in >>> MIME-encoded form by using the "mpack" utility. To use this >>> feature, insert the command "ENCODING mime" before the "FILE" >>> command. To decode the response(s), you will need "munpack" or >>> a MIME-compliant mail reader. Different MIME-compliant mail readers >>> exhibit different behavior, especially when dealing with >>> "multipart" MIME messages (i.e. documents which have been split >>> up into multiple messages), so check your local documentation on >>> how to manipulate these messages. >>> >>> >>>Below is the data which will enable a MIME compliant mail reader >>>implementation to automatically retrieve the ASCII version of the >>>Internet-Draft. >>> >>> >>>------------------------------------------------------------------------ >>> >>>_______________________________________________ >>>Isis-wg mailing list >>>Isis-wg@ietf.org >>>https://www1.ietf.org/mailman/listinfo/isis-wg >> >> >>_______________________________________________ >>Isis-wg mailing list >>Isis-wg@ietf.org >>https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Sat Nov 26 09:16:12 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eg0qa-0005re-V2; Sat, 26 Nov 2005 09:16:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EffZL-0008OG-KU; Fri, 25 Nov 2005 10:32:59 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08125; Fri, 25 Nov 2005 10:32:18 -0500 (EST) Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Effsc-0002bm-Ku; Fri, 25 Nov 2005 10:52:55 -0500 Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 25 Nov 2005 16:32:49 +0100 Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id jAPFWhAT021375; Fri, 25 Nov 2005 16:32:44 +0100 (MET) Received: from [10.61.81.249] (ams-clip-vpn-dhcp4602.cisco.com [10.61.81.249]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA04671; Fri, 25 Nov 2005 15:32:35 GMT Message-ID: <43872E92.2090600@cisco.com> Date: Fri, 25 Nov 2005 15:32:34 +0000 From: Stewart Bryant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: JP Vasseur References: <43CEE596-A350-4883-A85E-A889F5DC4FEC@cisco.com> In-Reply-To: <43CEE596-A350-4883-A85E-A889F5DC4FEC@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 26 Nov 2005 09:16:11 -0500 Cc: ccamp@ops.ietf.org, mpls@ietf.org, "David Kessens \(E-mail\)" , pce@ietf.org, isis-wg@ietf.org, idr@ietf.org, Bill Fenner , "Bert \(Bert\) Wijnen" , "raymond.zhang" , Mailing List Subject: [Isis-wg] Re: [Pce] Discussion on Multi-technology protection/restoration schemes X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org > Raymond Zhang, Jean-Louis Le Roux and myself have been discussing for > a while about the idea of the formation of a new Working Group at the > IETF (under the OPS area) in order to discuss operational issues > related to the use of multi-technologies in the context of > protection/restoration. This was motivated by a number of discussions > that we had with Service Providers expressing some interest in this > topic. > > For the sake of illustration, > (1) How to use Fast IGP in conjunction with MPLS TE FRR ? > (2) How to use Graceful Restart with Fast IGP or IPFRR ? > (3) Multi-technology protection/restoration OAM > - ... Would the wider application of loop-free IGP convergence as described in http://www.ietf.org/internet-drafts/draft-bryant-shand-lf-applicability-00.txt be in scope? - Stewart _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Sat Nov 26 09:16:52 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eg0rE-0005vN-B9; Sat, 26 Nov 2005 09:16:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Efeug-0007Ni-26; Fri, 25 Nov 2005 09:50:58 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03524; Fri, 25 Nov 2005 09:50:17 -0500 (EST) Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EffDv-0000y2-9B; Fri, 25 Nov 2005 10:10:53 -0500 Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 25 Nov 2005 06:50:46 -0800 X-IronPort-AV: i="3.97,377,1125903600"; d="scan'208,217"; a="678513587:sNHT38783728" Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id jAPEogs2026561; Fri, 25 Nov 2005 06:50:42 -0800 (PST) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 25 Nov 2005 09:50:41 -0500 Received: from [192.168.1.101] ([10.86.240.101]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 25 Nov 2005 09:50:40 -0500 Mime-Version: 1.0 (Apple Message framework v734) To: ccamp@ops.ietf.org, mpls@ietf.org, idr@ietf.org, Mailing List , isis-wg@ietf.org, pce@ietf.org Message-Id: <43CEE596-A350-4883-A85E-A889F5DC4FEC@cisco.com> From: JP Vasseur Date: Fri, 25 Nov 2005 09:50:08 -0500 X-Mailer: Apple Mail (2.734) X-OriginalArrivalTime: 25 Nov 2005 14:50:40.0769 (UTC) FILETIME=[9ACEB710:01C5F1CF] X-Spam-Score: 0.7 (/) X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac X-Mailman-Approved-At: Sat, 26 Nov 2005 09:16:51 -0500 Cc: LE ROUX Jean-Louis RD-CORE-LAN , Alex Zinin , "David Kessens \(E-mail\)" , Bill Fenner , "Bert \(Bert\) Wijnen" , "raymond.zhang" Subject: [Isis-wg] Discussion on Multi-technology protection/restoration schemes X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0574392760==" Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --===============0574392760== Content-Type: multipart/alternative; boundary=Apple-Mail-17-4186124 --Apple-Mail-17-4186124 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit Dear WGs, Raymond Zhang, Jean-Louis Le Roux and myself have been discussing for a while about the idea of the formation of a new Working Group at the IETF (under the OPS area) in order to discuss operational issues related to the use of multi-technologies in the context of protection/ restoration. This was motivated by a number of discussions that we had with Service Providers expressing some interest in this topic. For the sake of illustration, (1) How to use Fast IGP in conjunction with MPLS TE FRR ? (2) How to use Graceful Restart with Fast IGP or IPFRR ? (3) Multi-technology protection/restoration OAM - ... Indeed, there are many cases where such protection/restoration/HA technologies may interact thus triggering potential race conditions if not used appropriately. The aim of such potential Working Group would be to discuss these issues, document deployment models, ... and potentially come up with problem statements leading to new protocol requirements. Note that the goal of such WG would NOT be to work on protocol extensions but to analyze the problems statements, document combination strategies, ... Protocol extensions would be worked out in other WGs (likely in Routing area). We had a first informal meeting in Vancouver with: Bruno Decraene (FT), Eiji Oki (NTT), Yuichi Ikejiri (NTT), Kenji Kumaki (KDDI), Javier Achirica (Telefonica), Deborah Brungard (ATT), Jaime Miles (Level 3) and Alberto Tempia (Telecom Italia), Jean-Louis and myself. In this meeting, we got positive feed-back on the usefulness of this work. In the meantime we also received positive feed-back from a number of other Service Providers. A short ID should be posted soon proposing a problem statement. The OPS Area Directors (Bert and David) gave us the approval to create a mailing list to see whether this topic is of interest to the IETF community in which case a BOF may be approved for the next IETF. If you are interested, please join the mailing list and contribute to this work. mter@ietf.org: https://www1.ietf.org/mailman/listinfo/mter Thanks. JP, Jean-Louis and Raymond. --Apple-Mail-17-4186124 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Dear WGs,

Raymond = Zhang, Jean-Louis Le Roux and myself have been discussing for a while = about the idea of the formation of a new Working Group at the IETF = (under the OPS area) in order to discuss operational issues related to = the use of multi-technologies in the context of protection/restoration. = This was motivated by a number of discussions that we had with Service = Providers expressing some interest in this topic.=A0

For the sake = of illustration,
=A0 =A0 (1)=A0How to use Fast = IGP in conjunction with MPLS TE FRR ?
=A0 =A0 = (2)=A0How to use Graceful Restart with Fast IGP or IPFRR ?
=A0=A0=A0 (3)=A0Multi-technology = protection/restoration OAM=A0
=A0=A0 =A0 - = ...

Indeed, = there are many cases where such protection/restoration/HA technologies = may interact thus triggering potential race conditions if not used = appropriately.=A0

The aim of such potential Working Group would = be to discuss these issues, document deployment models, ... and = potentially come up with problem statements leading to new protocol = requirements. Note that the goal of such WG would NOT be to work on = protocol extensions but to analyze the problems statements, document = combination strategies, ... Protocol extensions would be worked out = in other WGs (likely in Routing area).

We had a = first informal meeting in Vancouver with: Bruno Decraene (FT), Eiji Oki = (NTT), Yuichi Ikejiri (NTT), Kenji Kumaki (KDDI), Javier Achirica = (Telefonica), Deborah Brungard (ATT), Jaime Miles (Level 3) and Alberto = Tempia (Telecom Italia), Jean-Louis and myself. In this meeting, we got = positive feed-back on the usefulness of this work.=A0

In the = meantime we also received positive feed-back from a number of other = Service Providers.

A short = ID should be posted soon proposing a problem statement.

The OPS Area = Directors (Bert and David) gave us the approval to create a mailing list = to see whether this topic is of interest to the IETF community in which = case a BOF may be approved for the next IETF. If you are interested, = please join the mailing list and contribute to this work.
=A0=A0=A0 mter@ietf.org:=A0<= A href=3D"https://www1.ietf.org/mailman/listinfo/mter">https://www1.ietf.org/mailman/listinfo/mter


JP, = Jean-Louis and Raymond.
= --Apple-Mail-17-4186124-- --===============0574392760== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --===============0574392760==--