From isis-wg-bounces@ietf.org Wed Sep 1 13:18:34 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12405 for ; Wed, 1 Sep 2004 13:18:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2XaJ-0003VW-Lk; Wed, 01 Sep 2004 12:03:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2WvH-0006Wd-04 for isis-wg@megatron.ietf.org; Wed, 01 Sep 2004 11:21:19 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26155 for ; Wed, 1 Sep 2004 11:21:12 -0400 (EDT) From: jcucchiara@mindspring.com Received: from blount.mail.mindspring.net ([207.69.200.226]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2WxP-0005ia-Qc for isis-wg@ietf.org; Wed, 01 Sep 2004 11:23:33 -0400 Received: from [192.168.167.41] (helo=wamui03.slb.atl.earthlink.net) by blount.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1C2Wv5-0001wr-00; Wed, 01 Sep 2004 11:21:07 -0400 Message-ID: <8129149.1094052067224.JavaMail.root@wamui03.slb.atl.earthlink.net> Date: Wed, 1 Sep 2004 11:21:06 -0400 (GMT-04:00) To: jparker@axiowave.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Earthlink Zoo Mail 1.0 X-Spam-Score: 0.3 (/) X-Scan-Signature: a8a20a483a84f747e56475e290ee868e Content-Transfer-Encoding: 7bit Cc: isis-wg@ietf.org Subject: [Isis-wg] few more questions on draft-ietf-isis-wg-mib-16.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jcucchiara@mindspring.com 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 Content-Transfer-Encoding: 7bit Hi Jeff, Just wanted to follow up on the Index values for some of the tables. The isisCircIndex, needs to be changed to IndexInteger TC from the DIFFSERV-MIB. isisCircIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) Please replace the above with isisCircIndex OBJECT-TYPE SYNTAX IndexInteger -- The following indices seem to have somewhat random terminating values. If there is a reason for the choosen value, could this be described in the DESCRIPTION clause for that index? isisLSPTLVIndex OBJECT-TYPE SYNTAX Unsigned32 (1..1000000) isisCircIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) isisISAdjIndex OBJECT-TYPE SYNTAX Integer32 (1..2000000000) isisISAdjAreaAddrIndex OBJECT-TYPE SYNTAX Integer32 (1..2000000000) isisISAdjIPAddrIndex OBJECT-TYPE SYNTAX Integer32 (1..2000000000) isisRAIndex OBJECT-TYPE SYNTAX Integer32 (1..2000000000) isisIPRANextHopIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) The mib review guidelines state: " - Unsigned32 with a range that excludes zero is RECOMMENDED for most index objects. It is acceptable to include zero in the range when it is semantically significant or when it is used as the index value for a unique row with special properties. Such usage SHOULD be clearly documented in the DESCRIPTION clause." If there is no reasons for these specific terminating values, then could the above indices be changed to Unsigned32(1..4294967295)? Separate question: Could the isisISAdjProtSuppProtocol object be added to the IsisISAdjEntry? The isisISAdjProtSuppTable and isisISAdjTable have the same indices of (isisCircIndex, isisISAdjIndex) and so moving the isisISAdjProtSuppProtocol object into the isisISAdjTable would simplify the MIB and more importantly, group information that is the same in the same table. One last question: the conformance statements should specify address types and lengths of addresses for example from rfc3289: OBJECT diffServMultiFieldClfrAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "An implementation is only required to support IPv4 and IPv6 addresses." OBJECT diffServMultiFieldClfrDstAddr SYNTAX InetAddress (SIZE(0|4|16)) DESCRIPTION "An implementation is only required to support IPv4 and globally unique IPv6 addresses." Also, if you could add a conformance for the RowStatus objects such that createAndWait and notInServer are not required that would be more flexible and especially appropriate for those tables that contain only a RowStatus object. For example from rfc3289: OBJECT diffServClfrStatus SYNTAX RowStatus { active(1) } WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } DESCRIPTION "Support for createAndWait and notInService is not required." thanks, Joan _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Sep 9 14:14:00 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09046 for ; Thu, 9 Sep 2004 14:13:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5TJ1-0000kn-IZ; Thu, 09 Sep 2004 14:05:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5T5c-0005nv-SF for isis-wg@megatron.ietf.org; Thu, 09 Sep 2004 13:52:09 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07436 for ; Thu, 9 Sep 2004 13:52:07 -0400 (EDT) Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5T9V-00070V-Nx for isis-wg@ietf.org; Thu, 09 Sep 2004 13:56:10 -0400 Message-ID: From: Bingzhang Zhao To: isis-wg@ietf.org Date: Thu, 9 Sep 2004 13:51:33 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Subject: [Isis-wg] question about MIB 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 Jeff, I'd like to suggest you to add "level" as an index to the table isisIPRATable. Without "level", I think the information carried in the table is incomplet. Thanks. Bingzhang _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Sep 16 15:22:16 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08035 for ; Thu, 16 Sep 2004 15:22:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C81hd-0007wx-92; Thu, 16 Sep 2004 15:13:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C81RX-0004V4-Qa for isis-wg@megatron.ietf.org; Thu, 16 Sep 2004 14:57:20 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05525 for ; Thu, 16 Sep 2004 14:57:17 -0400 (EDT) Received: from adsl-66-120-207-101.dsl.sntc01.pacbell.net ([66.120.207.101] helo=coffee.rawdofmt.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C81Wr-00085l-U6 for isis-wg@ietf.org; Thu, 16 Sep 2004 15:02:53 -0400 Received: from [IPv6:::1] (localhost [127.0.0.1]) by coffee.rawdofmt.org (Postfix) with ESMTP id F09933DCC8C for ; Thu, 16 Sep 2004 11:56:32 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v619) To: ISIS-WG (E-mail) Message-Id: <258D21D8-0812-11D9-AAE9-00039303E9E2@rawdofmt.org> Content-Type: multipart/mixed; boundary=Apple-Mail-1--1057798926 From: Christian Hopps Date: Thu, 16 Sep 2004 11:56:41 -0700 X-Mailer: Apple Mail (2.619) X-Spam-Score: 0.0 (/) X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd Subject: [Isis-wg] minutes that were sent for IETF60 proceedings 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 --Apple-Mail-1--1057798926 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit I've included the minutes below, unfortunately we couldn't have them reviewed by the list before sending them, maybe next time. --Apple-Mail-1--1057798926 Content-Type: text/plain; x-unix-mode=0444; name="isis-minutes.txt" Content-Disposition: attachment; filename=isis-minutes.txt Content-Transfer-Encoding: 7bit --- - ITU Liaison Statement Jonathan Sadler No Comments. --- - draft-ietf-isis-wg-mib-16.txt Removes multiple instances (MIB) Q: Why ? Chris: . not likely to be used unless in VPN context (done for VPN) . multiple instances will be supported in latest OSPF draft --- - draft-ietf-isis-experimental-tlv-03.txt presnted by Christian Hopps Dave: consensus to go to enterprise code --- - draft-ietf-isis-admin-tags-03.txt Stefano Previdi use of colouring in specific context (leaking for loo for MPLS VPN, fast convergence (route priority), ...) map BGP extended community => two different TLVs implementation, deployed WG document ? Acee: applications ? Stef: route distribution between levels, prioritize routes for ISIS (populating the RIB). Naiming: plan for IPv6 prefix ? Stef: no plan (IPv4 only). Will be done for IPv6 --- - draft-ietf-isis-igp-p2p-over-lan-04.txt Naiming Shen No significant changes, IESG comments incorporated Clarification done (unnumbered interfaces: remove the proxy-ARP ... ) Text added for IPv6, ND and OSPFv3 Chris: has been last called, just couple of comments form IESG ... Objection ? Floor: no --- - draft-ietf-isis-wg-multi-topology-07.txt Naiming Shen no major changes went trough LS and SD review once rev 06 -> rev -07 implemented by 3 vendors (Multicast Mutitopology and IPv6) Chris: which has been deployed rev 06 or rev -07 Naiming: ???? Old version (I guess) Chris: should issue a last call again since implementations are based on rev -06 --- - draft-shen-isis-interarea-route-attr-00.txt Naiming Shen Q: why use router-id of the next-hop frr A: router-id is not bundled to any interface it will allow more flexibility/stability. router may have multiple router-id Igor: is there any confidentiality issue in propagating the next-hop address into the level? Naiming: applications not entirely identified ... just a way to identify the NHOP's ABR Dave: go to the list before accepting as a WG document RTG WG needs first to conclude the FRR 3 drafts to color things ... becomes challenging Naiming: not limited Dave: need to clarify the application ... take to the list --- - draft-shen-isis-extended-tlv-00.txt Naiming Shen Chris: What problem are you trying to solve? Naiming: problem is not present now Chris: why don't we wait the problem first alex: there's about 70 years left for code points... Dimitri/Alex: TLV code is not the pb but the size of TLV Naiming: lots of info for GMPLS TLV for instance ... could be big Alex: possibility of backward compatible way ? ... TLV parsing error from non compatible ? Naiming: no they can skip the TLV Naiming: length no right ???Lenght (hi) = 0 ... so no interop issue Alex: will check the draft --- - draft-harrison-isis-ipv6-te-00.txt Jon Berger limited amount of people had read the draft Adrian: suggest input from CCAMP --- - draft-vasseur-isis-caps-00.txt Jean Philippe Vasseur merge of vasseur-iusis and raggarwa-isis drafts removed all management capabilities new capability tlv starting with router-id + flags + subTLVs propagation procedures/ interoperability requirements for capability tlv no issues wg doc ? Chris: decide on list. --- - draft-vasseur-isis-te-caps-00.txt Jean Philippe Vasseur Dave: send the conclusion of the PCE BOF to the list --- - draft-vasseur-isis-link-attr-01.txt Stefano Previdi Alia: like the idea of link sub-TLV, may not apply to IPFRR --- - RBRIDGE FYI session - pointer providing about the BOF Goal: glue links together to appear to be a single LAN to IP nodes Spanning tree does not prevent temporary loops, suboptimal IP routes to link, not end nodes ... Keep transparency to end node with 0 config (Bridge) with best path and no temporary loops (IP). Idea: link state protocol between RBridges + mechanism Tony Li: Status after the BOF: no technical compliant ... no real conclusion Radia: should it be in IEEE ? Dave: interest from ISIS WG ? Need for a new protocol or need to extend Link State --- - MERGED STDS TRACK DOCUMENT: RFC1195 + Domain + Extension for TE + IP interoprable: interest in creating a new doc related to IS-IS IP routing Tony Li: any change ? Chris: no, just merged draft, part of standard track, take to the list, Suresh: what is the goal ? Should it apply to IPv6 as well (TE for instance) Chis: all of them are IPv4 .... Not known for IPv6 More convenient to have a single document, that's all. Alex: question for the WG: better to have one unified spec for implementors? Henke Shenk: why not proceed each one individually as standard track Acee: emotional issue of obsleting doc that people did ... Henke Shenk: why does this question come up ? Does not make sense Chris: IP interop is a delta document, compilcates finding information. John: let them separate Dave: to the list .... --Apple-Mail-1--1057798926 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Chris. --Apple-Mail-1--1057798926 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --Apple-Mail-1--1057798926-- From isis-wg-bounces@ietf.org Thu Sep 16 15:23:54 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08185 for ; Thu, 16 Sep 2004 15:23:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C81it-0000CB-Vo; Thu, 16 Sep 2004 15:15:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C81VI-0007Ha-Jr for isis-wg@megatron.ietf.org; Thu, 16 Sep 2004 15:01:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05956 for ; Thu, 16 Sep 2004 15:01:10 -0400 (EDT) Received: from adsl-66-120-207-101.dsl.sntc01.pacbell.net ([66.120.207.101] helo=coffee.rawdofmt.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C81ag-0008CK-6e for isis-wg@ietf.org; Thu, 16 Sep 2004 15:06:46 -0400 Received: from [IPv6:::1] (localhost [127.0.0.1]) by coffee.rawdofmt.org (Postfix) with ESMTP id 9BBE93DCC8C for ; Thu, 16 Sep 2004 12:00:33 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: ISIS-WG (E-mail) From: Christian Hopps Date: Thu, 16 Sep 2004 12:00:42 -0700 X-Mailer: Apple Mail (2.619) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Content-Transfer-Encoding: 7bit Subject: [Isis-wg] Rough consensus at IETF60 on no merged base spec 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 Content-Transfer-Encoding: 7bit It was clear that at IETF60 we had a rough consensus on not merging the various standards track documents into a single base spec RFC. This is a final opportunity to comment on that before we will be publishing some of the documents (e.g., the IPv6 one) on their own std track. Chris. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Mon Sep 27 05:27:20 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14874 for ; Mon, 27 Sep 2004 05:27:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CBrlK-0007sf-Bn; Mon, 27 Sep 2004 05:25:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CBrgJ-0007Wm-7x for isis-wg@megatron.ietf.org; Mon, 27 Sep 2004 05:20:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14637 for ; Mon, 27 Sep 2004 05:20:24 -0400 (EDT) Received: from rproxy.gmail.com ([64.233.170.203] helo=mproxy.gmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CBrnt-0001Ye-2H for isis-wg@ietf.org; Mon, 27 Sep 2004 05:28:18 -0400 Received: by mproxy.gmail.com with SMTP id 75so3208423rnk for ; Mon, 27 Sep 2004 02:20:25 -0700 (PDT) Received: by 10.38.2.75 with SMTP id 75mr16608rnb; Mon, 27 Sep 2004 02:20:25 -0700 (PDT) Received: by 10.38.102.60 with HTTP; Mon, 27 Sep 2004 02:20:25 -0700 (PDT) Message-ID: Date: Mon, 27 Sep 2004 14:50:25 +0530 From: Abhishek Verma To: isis-wg@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7bit Subject: [Isis-wg] RFC 3784! X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Abhishek Verma 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 Content-Transfer-Encoding: 7bit Hi, The max size of a TLV in ISIS can be 255. Thus the number of IP prefixes that we can fit inside one TLV 128/130 is given by: Bytes needed to encode each prefix = 12 (metric+address+mask) 255/12 = 21 approx However, if we use 3784 encoding then number of IP prefixes that we can encode in each TLV 135 is 255/9 = 28 approx. Obviously, i assume in the latter case that there are no sub TLVs used. Does this imply that i can carry greater number of IP prefixes if i use TLV 135 (wide metrics) if no other TE feature is used? Regards, Abhishek V. P.S. For the sake of simplicity, i have ignored all the TLV header overheads, etc. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Mon Sep 27 09:14:24 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27571 for ; Mon, 27 Sep 2004 09:14:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CBv7H-0003pz-7D; Mon, 27 Sep 2004 09:00:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CBuxX-0002j5-MP for isis-wg@megatron.ietf.org; Mon, 27 Sep 2004 08:50:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26386 for ; Mon, 27 Sep 2004 08:50:25 -0400 (EDT) Received: from knint.xs4all.nl ([80.126.131.119]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CBv59-0005FT-Qw for isis-wg@ietf.org; Mon, 27 Sep 2004 08:58:20 -0400 Received: from knint.xs4all.nl (localhost.localdomain [127.0.0.1]) by knint.xs4all.nl (8.12.8/8.12.8) with ESMTP id i8RCoGx3001074; Mon, 27 Sep 2004 14:50:16 +0200 Received: (from henk@localhost) by knint.xs4all.nl (8.12.8/8.12.8/Submit) id i8RCoG1D001071; Mon, 27 Sep 2004 14:50:16 +0200 From: Henk Smit Message-Id: <200409271250.i8RCoG1D001071@knint.xs4all.nl> Subject: Re: [Isis-wg] RFC 3784! To: abhishekv.verma@gmail.com Date: Mon, 27 Sep 2004 14:50:16 +0200 (CEST) In-Reply-To: from "Abhishek Verma" at Sep 27, 2004 02:50:25 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb 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 Content-Transfer-Encoding: 7bit > The max size of a TLV in ISIS can be 255. Thus the number of IP > prefixes that we can fit inside one TLV 128/130 is given by: > > Bytes needed to encode each prefix = 12 (metric+address+mask) > 255/12 = 21 approx Correct. > However, if we use 3784 encoding then number of IP prefixes that we > can encode in each TLV 135 is 255/9 = 28 approx. It's even better. I see you count 5 bytes required to describe a prefix. One byte for prefix length, and 4 bytes for the prefix itself. Note that you only need 4 bytes if the prefix is 25 bits or longer. So for most routes in the Internet you will need 3 bytes or less. Therefor I think you can say that on average, you can fit 255/8 = 31 prefixes in a TLV. > Obviously, i assume in the latter case that there are no sub TLVs used. > > Does this imply that i can carry greater number of IP prefixes if i > use TLV 135 (wide metrics) if no other TE feature is used? Yes. This was one of the design considerations of the new TLVs. Henk. > Regards, > Abhishek V. > > P.S. > For the sake of simplicity, i have ignored all the TLV header overheads, etc. > > _______________________________________________ > 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 Mon Sep 27 12:48:52 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12091 for ; Mon, 27 Sep 2004 12:48:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CBySb-0004bM-9K; Mon, 27 Sep 2004 12:34:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAb8i-00025j-45 for isis-wg@megatron.ietf.org; Thu, 23 Sep 2004 17:28:32 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24984 for ; Thu, 23 Sep 2004 17:28:29 -0400 (EDT) Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAbFY-0002fF-Jj for isis-wg@ietf.org; Thu, 23 Sep 2004 17:35:37 -0400 Message-ID: <6A08876E69B0D6119284000255917A36B80B42@c3po.axiowave.com> From: Wenken Ling To: "'isis-wg@ietf.org'" Date: Thu, 23 Sep 2004 17:30:11 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 X-Mailman-Approved-At: Mon, 27 Sep 2004 12:34:43 -0400 Subject: [Isis-wg] question 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, Can someone supply me with a pointer to any ISIS WG documents for work related to isis for ipv6? I don't see anything that corresponds to this under the list of I-Ds & RFCs under the ISIS ietf web site. thanks, Wenken Ling _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Mon Sep 27 18:35:24 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16617 for ; Mon, 27 Sep 2004 18:35:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CC3yn-0001aa-OD; Mon, 27 Sep 2004 18:28:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CC3ua-0001Im-Ms for isis-wg@megatron.ietf.org; Mon, 27 Sep 2004 18:24:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16170 for ; Mon, 27 Sep 2004 18:23:57 -0400 (EDT) Received: from firestar.cisco.com ([171.68.227.75] helo=fire.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CC42I-0002AG-3Q for isis-wg@ietf.org; Mon, 27 Sep 2004 18:31:58 -0400 Received: from sj-cse-138.cisco.com (sj-cse-138.cisco.com [171.69.98.126]) by fire.cisco.com (8.11.7+Sun/8.8.8) with ESMTP id i8RMNKC19816; Mon, 27 Sep 2004 15:23:20 -0700 (PDT) Date: Mon, 27 Sep 2004 15:23:20 -0700 (PDT) From: Shankar Vemulapalli To: Wenken Ling Subject: Re: [Isis-wg] question In-Reply-To: <6A08876E69B0D6119284000255917A36B80B42@c3po.axiowave.com> Message-ID: References: <6A08876E69B0D6119284000255917A36B80B42@c3po.axiowave.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 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 Well, there is one that I know... which looks like expired now. It is: http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-06.txt You may want to check with the author on its current state.. Thanks, /Shankar At 5:30pm 09/23/04 -0400, Wenken Ling wrote: > Hi, > > Can someone supply me with a pointer to any ISIS WG documents for work > related to isis for ipv6? > I don't see anything that corresponds to this under the list of I-Ds & RFCs > under the ISIS ietf web site. > > thanks, > Wenken Ling > > _______________________________________________ > 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 Tue Sep 28 01:39:29 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13697 for ; Tue, 28 Sep 2004 01:39:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCAfD-0000tV-LN; Tue, 28 Sep 2004 01:36:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCAeX-0000go-MR for isis-wg@megatron.ietf.org; Tue, 28 Sep 2004 01:35:53 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13537 for ; Tue, 28 Sep 2004 01:35:52 -0400 (EDT) Received: from rproxy.gmail.com ([64.233.170.196] helo=mproxy.gmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCAmI-0001jH-FX for isis-wg@ietf.org; Tue, 28 Sep 2004 01:43:55 -0400 Received: by mproxy.gmail.com with SMTP id 75so3922087rnl for ; Mon, 27 Sep 2004 22:35:51 -0700 (PDT) Received: by 10.38.165.31 with SMTP id n31mr667417rne; Mon, 27 Sep 2004 22:35:51 -0700 (PDT) Received: by 10.38.102.60 with HTTP; Mon, 27 Sep 2004 22:35:51 -0700 (PDT) Message-ID: Date: Tue, 28 Sep 2004 11:05:51 +0530 From: Abhishek Verma To: Henk Smit Subject: Re: [Isis-wg] RFC 3784! In-Reply-To: <200409271250.i8RCoG1D001071@knint.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200409271250.i8RCoG1D001071@knint.xs4all.nl> X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7bit Cc: isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Abhishek Verma 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 Content-Transfer-Encoding: 7bit [clipped] > > Does this imply that i can carry greater number of IP prefixes if i > > use TLV 135 (wide metrics) if no other TE feature is used? > > Yes. > This was one of the design considerations of the new TLVs. Which means that we can carry more number of adjacencies in each TLV if we use wide-metrics! Thanks a lot! Abhishek. -- Class of 2004 Institute of Technology, BHU Varanasi, India _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Tue Sep 28 07:18:25 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13541 for ; Tue, 28 Sep 2004 07:18:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCFwW-00039f-Ja; Tue, 28 Sep 2004 07:14:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCFrD-0002Ss-PA for isis-wg@megatron.ietf.org; Tue, 28 Sep 2004 07:09:22 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13121 for ; Tue, 28 Sep 2004 07:09:16 -0400 (EDT) Received: from relay3.mail.uk.clara.net ([80.168.70.143]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCFz1-0006v1-Cg for isis-wg@ietf.org; Tue, 28 Sep 2004 07:17:24 -0400 Received: from du-069-0272.access.clara.net ([217.158.145.18] helo=Puppy) by relay3.mail.uk.clara.net with smtp (Exim 4.34) id 1CCFr6-000H6i-G2; Tue, 28 Sep 2004 12:09:13 +0100 Message-ID: <04eb01c4a54b$98b92fe0$42849ed9@Puppy> From: "Adrian Farrel" To: "Shankar Vemulapalli" , "Wenken Ling" , , References: <6A08876E69B0D6119284000255917A36B80B42@c3po.axiowave.com> Subject: Re: [Isis-wg] question Date: Tue, 28 Sep 2004 12:08:46 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Score: 0.1 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit Cc: isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel 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 Content-Transfer-Encoding: 7bit Hi, The I-D tracker shows that this draft has left the WG and is with the AD in state "AD is watching" after going through IETF last call in the middle of 2003. The comment says "The WG needs to make a decision on whether this should go STD track. Changing the state accordingly." This was in May this year. Since the draft has been through last call, it should not have expired. Chris/Dave, what's the status? Thanks, Adrian ----- Original Message ----- From: "Shankar Vemulapalli" To: "Wenken Ling" Cc: Sent: Monday, September 27, 2004 11:23 PM Subject: Re: [Isis-wg] question > Well, there is one that I know... which looks like expired now. > It is: http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-06.txt > You may want to check with the author on its current state.. > > Thanks, > > /Shankar > > At 5:30pm 09/23/04 -0400, Wenken Ling wrote: > > > Hi, > > > > Can someone supply me with a pointer to any ISIS WG documents for work > > related to isis for ipv6? > > I don't see anything that corresponds to this under the list of I-Ds & RFCs > > under the ISIS ietf web site. > > > > thanks, > > Wenken Ling > > > > _______________________________________________ > > 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 Tue Sep 28 08:53:34 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19094 for ; Tue, 28 Sep 2004 08:53:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCHMz-0000Mu-OJ; Tue, 28 Sep 2004 08:46:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCHFM-0007UE-Ga for isis-wg@megatron.ietf.org; Tue, 28 Sep 2004 08:38:20 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18113 for ; Tue, 28 Sep 2004 08:38:18 -0400 (EDT) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCHNA-0000G7-UL for isis-wg@ietf.org; Tue, 28 Sep 2004 08:46:26 -0400 Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 28 Sep 2004 08:55:02 -0400 X-BrightmailFiltered: true Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i8SCbj7A029690; Tue, 28 Sep 2004 08:37:45 -0400 (EDT) Received: from jlearman-w2k02.cisco.com (rtp-vpn3-90.cisco.com [10.82.216.90]) by fruitpie.cisco.com (MOS 3.4.6-GR) with ESMTP id BCH62798; Tue, 28 Sep 2004 05:37:44 -0700 (PDT) Message-Id: <4.3.2.7.2.20040928081003.02807608@dingdong.cisco.com> X-Sender: jlearman@dingdong.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 28 Sep 2004 08:15:19 -0400 To: Abhishek Verma , Henk Smit From: Jeff Learman Subject: Re: [Isis-wg] RFC 3784! In-Reply-To: References: <200409271250.i8RCoG1D001071@knint.xs4all.nl> <200409271250.i8RCoG1D001071@knint.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f 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 Just keep in mind that your system may not interoperate well with older implementations that don't support the TE TLV. Remember that the rule is you're allowed to ignore TLVs you don't recognize. This might lead to some serious black-hole issues. I haven't studied the TE RFC and I don't know how these issues are addressed. I'd guess it has something to do with transitioning all routers in a subdomain to wide metrics. Jeff At 01:35 AM 9/28/2004, Abhishek Verma wrote: >[clipped] > >> > Does this imply that i can carry greater number of IP prefixes if i >> > use TLV 135 (wide metrics) if no other TE feature is used? >> >> Yes. >> This was one of the design considerations of the new TLVs. > >Which means that we can carry more number of adjacencies in each TLV >if we use wide-metrics! > >Thanks a lot! > >Abhishek. > >-- >Class of 2004 >Institute of Technology, BHU >Varanasi, India > >_______________________________________________ >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 Sep 30 09:52:17 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21609 for ; Thu, 30 Sep 2004 09:52:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD1DX-00076P-8G; Thu, 30 Sep 2004 09:43:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCIYX-0000hU-Fq for isis-wg@megatron.ietf.org; Tue, 28 Sep 2004 10:02:13 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23509 for ; Tue, 28 Sep 2004 10:02:11 -0400 (EDT) Received: from anthrax.middlebury.edu ([140.233.2.72]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCIgK-0001w2-0E for isis-wg@ietf.org; Tue, 28 Sep 2004 10:10:19 -0400 Received: from arcticcat.middlebury.edu [140.233.2.8] by anthrax.middlebury.edu with XWall v3.30 ; Tue, 28 Sep 2004 10:01:34 -0400 Received: from GRASSHOPPER.middlebury.edu ([140.233.2.6]) by arcticcat.middlebury.edu with Microsoft SMTPSVC(5.0.2195.6713); Tue, 28 Sep 2004 10:01:34 -0400 Received: GRASSHOPPER 140.233.2.6 from 140.233.20.185 140.233.20.185 via HTTP with MS-WebStorage 6.0.6249 User-Agent: Microsoft-Entourage/11.0.0.040405 Date: Tue, 28 Sep 2004 10:01:32 -0400 Subject: Re: [Isis-wg] RFC 3784! From: "Parker, Jeff" To: Jeff Learman , Abhishek Verma , Henk Smit Message-ID: In-Reply-To: <4.3.2.7.2.20040928081003.02807608@dingdong.cisco.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 28 Sep 2004 14:01:34.0281 (UTC) FILETIME=[A9D41390:01C4A563] X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 30 Sep 2004 09:43:29 -0400 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 Content-Transfer-Encoding: 7bit Not sure that this mail will make it through to the wg list, as this is from my "wrong" account. The issue of interoperation is flagged in the IP Interoperation RFC, and a transition strategy was described - jeff parker On 9/28/04 8:15 AM, "Jeff Learman" wrote: > > Just keep in mind that your system may not interoperate well > with older implementations that don't support the TE TLV. Remember > that the rule is you're allowed to ignore TLVs you don't recognize. > This might lead to some serious black-hole issues. I haven't studied > the TE RFC and I don't know how these issues are addressed. I'd guess > it has something to do with transitioning all routers in a subdomain > to wide metrics. > > Jeff > > At 01:35 AM 9/28/2004, Abhishek Verma wrote: >> [clipped] >> >>>> Does this imply that i can carry greater number of IP prefixes if i >>>> use TLV 135 (wide metrics) if no other TE feature is used? >>> >>> Yes. >>> This was one of the design considerations of the new TLVs. >> >> Which means that we can carry more number of adjacencies in each TLV >> if we use wide-metrics! >> >> Thanks a lot! >> >> Abhishek. >> >> -- >> Class of 2004 >> Institute of Technology, BHU >> Varanasi, India >> >> _______________________________________________ >> 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 Thu Sep 30 10:09:18 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23255 for ; Thu, 30 Sep 2004 10:09:18 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD1Rz-0002R8-P2; Thu, 30 Sep 2004 09:58:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD1Hz-00086L-Cu for isis-wg@megatron.ietf.org; Thu, 30 Sep 2004 09:48:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21400 for ; Thu, 30 Sep 2004 09:48:04 -0400 (EDT) Received: from adsl-66-120-207-101.dsl.sntc01.pacbell.net ([66.120.207.101] helo=coffee.rawdofmt.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CD1Q4-0008JS-Jo for isis-wg@ietf.org; Thu, 30 Sep 2004 09:56:39 -0400 Received: from [IPv6:::1] (localhost [127.0.0.1]) by coffee.rawdofmt.org (Postfix) with ESMTP id 00CE93DCC8C; Thu, 30 Sep 2004 06:47:23 -0700 (PDT) In-Reply-To: <04eb01c4a54b$98b92fe0$42849ed9@Puppy> References: <6A08876E69B0D6119284000255917A36B80B42@c3po.axiowave.com> <04eb01c4a54b$98b92fe0$42849ed9@Puppy> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <41CFBA18-12E7-11D9-BDBB-000D93C60674@rawdofmt.org> Content-Transfer-Encoding: 7bit From: Christian Hopps Subject: Re: [Isis-wg] question Date: Thu, 30 Sep 2004 06:47:23 -0700 To: Adrian Farrel X-Mailer: Apple Mail (2.619) X-Spam-Score: 0.0 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a Content-Transfer-Encoding: 7bit Cc: Wenken Ling , Shankar Vemulapalli , isis-wg@ietf.org, dward@cisco.com 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 Content-Transfer-Encoding: 7bit The draft has been ressurected. Since we decided to take this draft standards track it will need an implementation report and a standardization report apparently before being published as an RFC. Chris. On Sep 28, 2004, at 4:08 AM, Adrian Farrel wrote: > Hi, > > The I-D tracker shows that this draft has left the WG and is with the > AD in state "AD is > watching" after going through IETF last call in the middle of 2003. > The comment says "The WG needs to make a decision on whether this > should go STD track. > Changing the state accordingly." > This was in May this year. > > Since the draft has been through last call, it should not have expired. > > Chris/Dave, what's the status? > > Thanks, > Adrian > ----- Original Message ----- > From: "Shankar Vemulapalli" > To: "Wenken Ling" > Cc: > Sent: Monday, September 27, 2004 11:23 PM > Subject: Re: [Isis-wg] question > > >> Well, there is one that I know... which looks like expired now. >> It is: >> http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-06.txt >> You may want to check with the author on its current state.. >> >> Thanks, >> >> /Shankar >> >> At 5:30pm 09/23/04 -0400, Wenken Ling wrote: >> >>> Hi, >>> >>> Can someone supply me with a pointer to any ISIS WG documents for >>> work >>> related to isis for ipv6? >>> I don't see anything that corresponds to this under the list of I-Ds >>> & RFCs >>> under the ISIS ietf web site. >>> >>> thanks, >>> Wenken Ling >>> >>> _______________________________________________ >>> 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 _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Sep 30 14:18:58 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16143 for ; Thu, 30 Sep 2004 14:18:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD59k-00060W-SB; Thu, 30 Sep 2004 13:55:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD4z5-00030k-D9 for isis-wg@megatron.ietf.org; Thu, 30 Sep 2004 13:44:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13293 for ; Thu, 30 Sep 2004 13:44:49 -0400 (EDT) Received: from adsl-66-120-207-101.dsl.sntc01.pacbell.net ([66.120.207.101] helo=coffee.rawdofmt.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CD57D-0006F1-81 for isis-wg@ietf.org; Thu, 30 Sep 2004 13:53:25 -0400 Received: from [IPv6:::1] (localhost [127.0.0.1]) by coffee.rawdofmt.org (Postfix) with ESMTP id AD6F03DCC8C; Thu, 30 Sep 2004 10:44:08 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <547FDDCE-1308-11D9-BDBB-000D93C60674@rawdofmt.org> Content-Transfer-Encoding: 7bit From: Christian Hopps Date: Thu, 30 Sep 2004 10:44:08 -0700 To: ISIS-WG (E-mail) X-Mailer: Apple Mail (2.619) X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: 7bit Cc: Jeff Parker Subject: [Isis-wg] MIB again :) 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 Content-Transfer-Encoding: 7bit Ok I made the bold claim that we would be done with the MIB by this month. I think it's fair to say we won't be able to achieve that goal. Anyway, I'd like to come to an understanding about what we think the open issues are and close them. A brief read through my mailbox highlighted at least a couple issues: 1) Protocol supported . Should we use a BITS scalar? . Should we have 2 scalars, "Supported" and "Enabled"? 2) isisCircLevelEntry/isisSyslevelEntry Rows . Should the values in the isisCircLevelEntrys be read-write or read-create For 1) Yes to both seems reasonable to me. I didn't see anyway comment on this and the thread sort of died before this was answered. For 2) my understanding with the isisCircLevelEntry (similar for isisSysLevelEntry) is that currently the rows will be created *if they don't exist already* according to what the user has set isisCircLevel to in the isisCircEntry Row for the given circuit; however, the user could create (read-create access) a value in a isisCircLevelEntry row to configure a row that isn't supported by the isisCircLevel value in the isisCircEntry. This seems somewhat useful, but complex. Are there examples of this in other protocol MIBs? IANAME (I am not a MIB expert). Chris. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Sep 30 14:58:59 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19021 for ; Thu, 30 Sep 2004 14:58:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD5q4-0000Oy-0a; Thu, 30 Sep 2004 14:39:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD5g5-0005Zh-59; Thu, 30 Sep 2004 14:29:17 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16638; Thu, 30 Sep 2004 14:29:15 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CD5oN-0007Ip-QY; Thu, 30 Sep 2004 14:37:51 -0400 Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1CD5QI-000234-1Y; Thu, 30 Sep 2004 14:12:58 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Thu, 30 Sep 2004 14:12:58 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Cc: Internet Architecture Board , isis chair , isis mailing list , isis chair , RFC Editor Subject: [Isis-wg] Document Action: 'Point-to-point operation over LAN in link-state routing protocols' to Informational RFC 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 The IESG has approved the following document: - 'Point-to-point operation over LAN in link-state routing protocols ' as an Informational RFC This document is the product of the IS-IS for IP Internets Working Group. The IESG contact persons are Bill Fenner and Alex Zinin. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Sep 30 17:08:43 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03132 for ; Thu, 30 Sep 2004 17:08:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD7h9-0005ri-1M; Thu, 30 Sep 2004 16:38:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD7PV-0005Jq-9f for isis-wg@megatron.ietf.org; Thu, 30 Sep 2004 16:20:17 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27671 for ; Thu, 30 Sep 2004 16:20:14 -0400 (EDT) Received: from [64.47.51.130] (helo=exchange.timetra.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CD7Xb-00022z-Ar for isis-wg@ietf.org; Thu, 30 Sep 2004 16:28:52 -0400 Received: from vpndg ([10.20.30.1] unverified) by exchange.timetra.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 30 Sep 2004 13:19:28 -0700 From: "Don Goodspeed" To: "Christian Hopps" , "ISIS-WG \(E-mail\)" Subject: RE: [Isis-wg] MIB again :) Date: Thu, 30 Sep 2004 13:23:41 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <547FDDCE-1308-11D9-BDBB-000D93C60674@rawdofmt.org> X-OriginalArrivalTime: 30 Sep 2004 20:19:28.0452 (UTC) FILETIME=[C9838040:01C4A72A] X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit Cc: Jeff Parker X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Don.Goodspeed@alcatel.com 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 Content-Transfer-Encoding: 7bit Christian, I had thought Jeff, Joan and I had come to some conclusions on these issues in line with your summations below. Jeff was then going to go back and make the revisions but this was when he left his former company and I don't think his address above will work any more. I did not have any more changes and at this time I don't think Joan does either (correct me if I'm wrong) other than what is outstanding. Cheers, Don -----Original Message----- From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org]On Behalf Of Christian Hopps Sent: Thursday, September 30, 2004 10:44 AM To: ISIS-WG (E-mail) Cc: Jeff Parker Subject: [Isis-wg] MIB again :) Ok I made the bold claim that we would be done with the MIB by this month. I think it's fair to say we won't be able to achieve that goal. Anyway, I'd like to come to an understanding about what we think the open issues are and close them. A brief read through my mailbox highlighted at least a couple issues: 1) Protocol supported . Should we use a BITS scalar? . Should we have 2 scalars, "Supported" and "Enabled"? 2) isisCircLevelEntry/isisSyslevelEntry Rows . Should the values in the isisCircLevelEntrys be read-write or read-create For 1) Yes to both seems reasonable to me. I didn't see anyway comment on this and the thread sort of died before this was answered. For 2) my understanding with the isisCircLevelEntry (similar for isisSysLevelEntry) is that currently the rows will be created *if they don't exist already* according to what the user has set isisCircLevel to in the isisCircEntry Row for the given circuit; however, the user could create (read-create access) a value in a isisCircLevelEntry row to configure a row that isn't supported by the isisCircLevel value in the isisCircEntry. This seems somewhat useful, but complex. Are there examples of this in other protocol MIBs? IANAME (I am not a MIB expert). Chris. _______________________________________________ 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