From isis-wg-admin@ietf.org Mon Dec 2 10:59:59 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21652 for ; Mon, 2 Dec 2002 10:59:59 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2Fwhv08559; Mon, 2 Dec 2002 10:58:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2Fvev08484 for ; Mon, 2 Dec 2002 10:57:40 -0500 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21180 for ; Mon, 2 Dec 2002 10:54:48 -0500 (EST) Message-ID: From: Jeff Parker To: "'Noguchi Kay'" , isis-wg@ietf.org Subject: RE: [Isis-wg] isisLSPTLVIndex MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 2 Dec 2002 10:57:27 -0500 > Hi Jeff, > > MAX-ACCESS attribute for isisLSPTLVIndex should be > not-accessible, instead > of read-only, because isisLSPTLVIndex is the index for the > isisLSPTLVEntry. > > Thank you, > > kay Kay - I just tried that, and SMICng complained. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Dec 3 08:12:56 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17935 for ; Tue, 3 Dec 2002 08:12:56 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB3DAIv06005; Tue, 3 Dec 2002 08:10:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB3D3Dv05139 for ; Tue, 3 Dec 2002 08:03:13 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17256; Tue, 3 Dec 2002 08:00:20 -0500 (EST) Message-Id: <200212031300.IAA17256@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-ipv6-04.txt Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 03 Dec 2002 08:00:20 -0500 --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 : Routing IPv6 with IS-IS Author(s) : C. Hopps Filename : draft-ietf-isis-ipv6-04.txt Pages : 7 Date : 2002-12-2 This draft specifies a method for exchanging IPv6 routing information using the IS-IS routing protocol. The described method utilizes 2 new TLVs, a reachability TLV and an interface address TLV to distribute the necessary IPv6 information throughout a routing domain. Using this method one can route IPv6 along with IPv4 and OSI using a single intra-domain routing protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-04.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-04.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-04.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: <2002-12-2140127.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-ipv6-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-ipv6-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-2140127.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Dec 4 13:32:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27220 for ; Wed, 4 Dec 2002 13:32:30 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB4IWGv09558; Wed, 4 Dec 2002 13:32:17 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB4IQ3v09260 for ; Wed, 4 Dec 2002 13:26:03 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26735; Wed, 4 Dec 2002 13:23:07 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1 ident=zinin) by psg.com with esmtp (Exim 3.36 #2) id 18JeDZ-000FGM-00; Wed, 04 Dec 2002 10:25:53 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.51) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <121158569851.20021204102519@psg.com> To: routing-discussion@ietf.org CC: isis-wg@ietf.org, OSPF@DISCUSS.MICROSOFT.COM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Isis-wg] Fwd: IETF Sub-IP area: request for input Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 4 Dec 2002 10:25:19 -0800 Content-Transfer-Encoding: 7bit FYI below. (Sorry for cross-posting.) Please post follow-ups to ietf@ietf.org. -- Alex This is a forwarded message From: The IESG To: Cc: Date: Wednesday, December 04, 2002, 8:08:49 AM Subject: IETF Sub-IP area: request for input ===8<==============Original message text=============== IETF SUB-IP area The IESG announced in November of 2000 that a new SUB-IP temporary pseudo-area would be formed as a part of an effort to develop a "systematic approach to dealing with what we used to describe as "sub-IP" technologies." At the time the IESG said: "Over the years the boundary between 'wires' and IP protocols has become harder to define and the interaction has become more intertwined. For example, what appear as 'wires' or 'circuits' in a virtual network may in fact be routed datagrams in an underlying IP network. The topology of dynamic underlying networks such as ATM and soon switched optical networks can interact with IP-level traffic engineering and routing. Additionally, with IETF technologies such as MPLS we are defining a whole new class of 'wires'." (http://www.ietf.org/IESG/STATEMENTS/new-area.txt) After the December 2000 IETF meeting and taking into account the discussion at that meeting the IESG formed a "temporary" SUB-IP Area. IN the announcement of this action the IESG said: "It is temporary because the IESG believes that this concentrated sub-IP effort will likely be of short duration, on the order of a year or two. We feel that much of the work will be done by then, and the working groups closed. Any working groups that have not finished when the IESG determines that the area should be closed will be moved into existing the IETF areas where they seem to have the best fit." and "The IESG expects to review the development process and charters, however; if we conclude that this expectation is incorrect, we will need to make this area more formal. At that point, the nominating committee will be asked to supply dedicated area directors." (http://www.ietf.org/IESG/STATEMENTS/sub_area.txt) Although the SUB-IP working groups have made considerable progress (with 7 RFCs published, another 12 IDs approved for publication, 9 IDs under IESG consideration and an additional 11 IDs having been passed to the ADs for their evaluation) their work is not yet done (with 53 working group IDs currently in progress). It does appear that some of the working groups could finish the work in their charters over the next 6 months but it could be a lot longer for others. Because the end is in sight for some of the working groups and since the IESG had generally assumed that the area would be a temporary one and the second anniversary of the creation of the SUB-IP area is next spring, analysis was started in the IESG to figure out which areas would be the best ones for the SUB-IP working groups to move to so that they could continue their work. As part of that analysis a SUB-IP area session was held during the IETF meeting in Atlanta where this topic was discussed. There was a spirited discussion during the session on the best path forward. The opinions ranged from following the distribution of working groups, to doing so with some specific changes to keeping the working groups in a separate SUB-IP area. A sense of the room was taken at the end of the discussion and that sense was very strongly that the SUB-IP Area should become a "long-term" (the description that was used during the consensus call) one and that the nomcom be asked to nominate a person (or persons) to become director(s) of the SUB-IP area. To help provide more information as input for the IESG discussion we would like to continue the discussion started in Atlanta on the mailing list. It is our intention to keep the discussion on the future of the SUB-IP area open, but short-lived, because it would be a very good idea to let the nomcom know ASAP what the future holds as they need to know what expertise is needed in the ADs for the existing areas and if they need to search for additional people. The IESG aim is to be able to let the nomcom know what the future of the SUB-IP work is by the end of the day of Thursday Dec 12th. That date was chosen because it is the date of the next IESG teleconference yet it provides some time for a public discussion. The options seem to be: 1/ move WGs (back) to permanent areas: migrate the SUB-IP working groups to other IETF areas sometime soon, likely before next summer and close the SUB-IP area. Also, reconstitute the SUB-IP (and/or other) directorates to ensure the continued coordination between the remaining WGs. 2/ establish a long-term area: decide that the SUB-IP area will be a long-term one, clearly define its charter, and ask the nomcom to select one or two people to be Area Directors 3/ status quo: continue the SUB-IP Area as a temporary, ad-hoc effort, much as it has been, with the IESG selecting two sitting ADs to continue the effort that Bert & Scott have been doing. But maybe give more responsibility to the working group's technical advisors, normally the AD from the area where the working group might otherwise live. Data points for the discussion: DP1. It does look like a number of the SUB-IP working groups will be finishing up their main work in the next year and be ready to be closed until it is time to revise the RFCs based on experience or to advance them on the standards track. The groups that should be finishing up include ipo, gsmp and tewg. That would leave mpls, ppvpn and ccamp. DP2. WGs in SUB-IP or the work pursued in them came from existing well-established areas, i.e., tewg came from OPS, gsmp, mpls (with ccamp and ppvpn as its derivatives) came from RTG. DP3. There's still a need for technical oversight from permanent areas, so some WGs have a technical advisor--normally the AD from the area where the working group might otherwise live (e.g. CCAMP, and PPVPN with a RTG AD as the TA). DP4. SUB-IP directorate was very useful when the area was just created. It is currently passive and WGs continue operating just fine. DP5. The sense of the SUB-IP session in Atlanta was that the SUB-IP Area was working and there is no compelling reason to break it up. There is a need to clarify the charters of some of the working groups so that the different groups understand what the division of tasks are but it is hard to identify what problem would be solved by breaking up the area. DP6. Extensions to specific IETF technologies should be done in the working groups responsible for those technologies based on requirements provided by other working groups. For example, extensions to OSPF should be done by the OSPF working group based on input from other working groups or individuals rather than being done someplace else. Discussions about the options: 1/ Move WGs (back) to permanent areas and close the area For: Each WG within SUB-IP definitely has a strong feature that maps it to a given permanent area [1]. The property that logically holds them together in SUB-IP now is the need for coordination wrt the technologies that are normally considered below the IP layer. While this was indeed necessary right after SUB-IP creation, DP4 suggests that the goal has been achieved and the focus is shifting back to coordination with permanent areas (e.g., DP3, as well as the fact that RTG WGs are already dealing with SUB-IP related extensions). DP1 suggests that there will be about three active WGs within a year; at least two of them can be argued to belong in RTG area (where they originally came from, see DP2), so it wouldn't make a lot of sense to have two separate areas overlapping so considerably. PPVPN does not map strongly to any area, however it doesn't map strongly to SUB-IP either (MPLS is just one possible encapsulation method) Against: DP5 suggests that the feeling in the room was against closing the area, though there was also some support for the idea that moving MPLS and CCAMP to RTG would be a fine idea if the area were to be closed. The feeling was that the area has been working and that there is no strong argument that there is a need to change things at this time. 2/ Establish a long-term area For: DP5 suggests that the community believes this is a good idea. See also the "Against" for option 1. In addition the opinion was expressed that having a specific area with specifically assigned management, knowledgeable in the field, would be an advantage. In addition, new SUP-IP work may develop in the future and it would be good to have a home for it. Against: See "For" arguments for option 1 above. Also, there was an assumption when the area was formed that it would be temporary and the size of the IESG is near max effective size. It is also expected that if the nomcom needs to find an AD(s) for SUB-IP, the set of required skills would be extremely similar to those needed for the RTG area, which again brings up the question of whether it makes sense to have two areas with so similar expertise scopes. 3/ Status quo For: DP5 suggests that the way the area operates is fine and does not need fixing at this time. As DP1 predicts, there may not be many active SUB-IP working groups within a year and it may be best to wait until a few of the working groups finish their work and close before deciding on the long term direction for this work. The IESG would decide which ADs would be asked to manage the area in March. Against: A decision has to be made sooner or later, delaying the decision will not make it any easier to make. The IESG would like to hear from the community on this topic - please direct your comments to the ietf@ietf.org list. The IESG will discuss the matter in its next telechat on December 12. -------------------------------------------------- [1] possible WG to area mappings: - IPO has the IP-over-foo property, which is usually addressed in INT, - GSMP came from RTG - MPLS (aside from the fact that it came from RTG) deals with a technology that is arguably another IP forwarding paradigm and relies heavily on regular routing functionality and/or protocols. - CCAMP works on a generalized version of MPLS, which could map it to RTG as well - TEWG came from O&M - PPVPN: suggestions have been made of INT, because its tunneling which is closest to INT, RTG because some of the suggested discovery and VPN routing mechanisms, and TSV, because its related to PWE3 (in TSV because of congestion control worries) ===8<===========End of original message text=========== _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Dec 9 08:07:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07698 for ; Mon, 9 Dec 2002 08:07:24 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB9D6qv31680; Mon, 9 Dec 2002 08:06:52 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB9D5cv31604 for ; Mon, 9 Dec 2002 08:05:38 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07180; Mon, 9 Dec 2002 08:02:41 -0500 (EST) Message-Id: <200212091302.IAA07180@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-gmpls-extensions-15.txt Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 09 Dec 2002 08:02:41 -0500 --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 : IS-IS Extensions in Support of Generalized MPLS Author(s) : K. Kompella, Y. Rekhter Filename : draft-ietf-isis-gmpls-extensions-15.txt Pages : 12 Date : 2002-12-6 This document specifies encoding of extensions to the IS-IS routing protocol in support of Generalized Multi-Protocol Label Switching. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-gmpls-extensions-15.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-gmpls-extensions-15.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-gmpls-extensions-15.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: <2002-12-6140306.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-gmpls-extensions-15.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-gmpls-extensions-15.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-6140306.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Dec 10 12:09:50 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13911 for ; Tue, 10 Dec 2002 12:09:49 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAH5cv11713; Tue, 10 Dec 2002 12:05:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBAGxOv11443 for ; Tue, 10 Dec 2002 11:59:24 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13596; Tue, 10 Dec 2002 11:56:25 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1 ident=zinin) by psg.com with esmtp (Exim 3.36 #2) id 18Lnj4-000A3d-00; Tue, 10 Dec 2002 08:59:18 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.51) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <56159511465.20021210085848@psg.com> To: routing-discussion@ietf.org CC: isis-wg@ietf.org, OSPF@DISCUSS.MICROSOFT.COM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Isis-wg] Fwd: Reminder: Deadline for input on sub-ip discussion Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 10 Dec 2002 08:58:48 -0800 Content-Transfer-Encoding: 7bit From the ietf-discussion list. -- Alex This is a forwarded message From: Harald Tveit Alvestrand To: ietf@ietf.org Cc: Date: Monday, December 09, 2002, 1:21:59 PM Subject: Reminder: Deadline for input on sub-ip discussion ===8<==============Original message text=============== All, On Wed Dec 4th, we asked for input to help us decide on the future of the SUB-IP Area. See our posting at http://www.ietf.org/mail-archive/ietf/Current/msg18370.html We had a large majority of people at the SUBIP Area meeting in Atlanta expressing that they want the area to be long(er) lived. This will be part of our input. But we need/want to hear from the IETF community. So please express your opionion (and the reasoning behind it) asap on ietf@ietf.org, but certainly before Thursday Dec 12th 10am US Eastern time. As expressed in the above posting (with data points and discussion included), the 3 choices for the SUB-IP Area seem to be: 1/ move WGs (back) to permanent areas: migrate the SUB-IP working groups to other IETF areas sometime soon, likely before next summer and close the SUB-IP area. Also, reconstitute the SUB-IP (and/or other) directorates to ensure the continued coordination between the remaining WGs. 2/ establish a long-term area: decide that the SUB-IP area will be a long-term one, clearly define its charter, and ask the nomcom to select one or two people to be Area Directors 3/ status quo: continue the SUB-IP Area as a temporary, ad-hoc effort, much as it has been, with the IESG selecting two sitting ADs to continue the effort that Bert & Scott have been doing. But maybe give more responsibility to the working group's technical advisors, normally the AD from the area where the working group might otherwise live. The opinions expressed so far seem to show clearly that the community is divided on the issue, with perhaps some preference for the status quo (alternative 3). If you have a strong preference for one (or two) of these, and have not yet said so, please indicate your opinion (and your reasons) by mail to ietf@ietf.org before Thursday. Thank you! Harald Alvestrand, for the IESG (please repost this message where appropriate) ===8<===========End of original message text=========== _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Fri Dec 20 07:22:05 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23519 for ; Fri, 20 Dec 2002 07:22:05 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKCMnv12403; Fri, 20 Dec 2002 07:22:50 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKCCgv11974 for ; Fri, 20 Dec 2002 07:12:42 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23023; Fri, 20 Dec 2002 07:09:17 -0500 (EST) Message-Id: <200212201209.HAA23023@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-traffic-04.txt Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 20 Dec 2002 07:09:16 -0500 --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 : IS-IS extensions for Traffic Engineering Author(s) : T. Li, H. Smit Filename : draft-ietf-isis-traffic-04.txt Pages : 11 Date : 2002-12-18 This document describes extensions to the IS-IS protocol to support Traffic Engineering. This document extends the IS-IS protocol by specifying new information that an Intermediate System [router] can place in Link State Protocol Data Units. This information describes additional details of the state of the network that are useful for traffic engineering computations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-traffic-04.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-traffic-04.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-traffic-04.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: <2002-12-18131941.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-traffic-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-traffic-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-18131941.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Fri Dec 20 14:54:33 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08275 for ; Fri, 20 Dec 2002 14:54:33 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKJtOv04647; Fri, 20 Dec 2002 14:55:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKJohv04433 for ; Fri, 20 Dec 2002 14:50:43 -0500 Received: from sj-msg-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07964 for ; Fri, 20 Dec 2002 14:47:13 -0500 (EST) Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34]) by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id gBKJoGfm025140 for ; Fri, 20 Dec 2002 11:50:16 -0800 (PST) Received: from ginsberg-w2k.cisco.com (sjc-vpn3-497.cisco.com [10.21.65.241]) by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA) with ESMTP id ADE81027; Fri, 20 Dec 2002 11:46:45 -0800 (PST) Message-Id: <4.3.2.7.2.20021220114336.00b363d0@mira-sjc5-3.cisco.com> X-Sender: ginsberg@mira-sjc5-3.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 To: isis-wg@ietf.org From: Les Ginsberg Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-traffic-04.txt In-Reply-To: <200212201209.HAA23023@ietf.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 20 Dec 2002 11:50:13 -0800 Was the version number of this draft (04) intentionally kept the same as the previous version dated August 2001? While I appreciate that the changes are largely editorial, this still seems confusing. Les At 07:09 AM 12/20/2002 -0500, 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 : IS-IS extensions for Traffic Engineering > Author(s) : T. Li, H. Smit > Filename : draft-ietf-isis-traffic-04.txt > Pages : 11 > Date : 2002-12-18 > >This document describes extensions to the IS-IS protocol to support >Traffic Engineering. >This document extends the IS-IS protocol by specifying new >information that an Intermediate System [router] can place in Link >State Protocol Data Units. This information describes additional >details of the state of the network that are useful for traffic >engineering computations. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-isis-traffic-04.txt > >To remove yourself from the IETF Announcement list, send a message to >ietf-announce-request with the word unsubscribe in the body of the message. > >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-traffic-04.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-traffic-04.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. >Content-Type: text/plain >Content-ID: <2002-12-18131941.I-D@ietf.org> _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Fri Dec 20 17:08:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13041 for ; Fri, 20 Dec 2002 17:08:30 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKM9Kv13258; Fri, 20 Dec 2002 17:09:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKM8qv13233 for ; Fri, 20 Dec 2002 17:08:52 -0500 Received: from dmz1.procket.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12922 for ; Fri, 20 Dec 2002 17:05:21 -0500 (EST) Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60]) by dmz1.procket.com (Postfix) with ESMTP id 1BCE823C4E; Fri, 20 Dec 2002 14:05:20 -0800 (PST) Received: from EXCHANGE0-0.na.procket.com (exchange0a.na.procket.com [10.1.7.7]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id gBKM8Nie028459; Fri, 20 Dec 2002 14:08:23 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Isis-wg] I-D ACTION:draft-ietf-isis-traffic-04.txt Message-ID: Thread-Topic: [Isis-wg] I-D ACTION:draft-ietf-isis-traffic-04.txt Thread-Index: AcKoYs5ZZzmVpjyPSniIzr3o5nGI9QAEXasA From: "Tony Li" To: "Les Ginsberg" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gBKM8qv13234 Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 20 Dec 2002 14:08:22 -0800 Content-Transfer-Encoding: 8bit | Was the version number of this draft (04) intentionally | kept the same as | the previous version dated August 2001? While I appreciate | that the changes | are largely editorial, this still seems confusing. No, sorry, silly bug. Tony _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Fri Dec 20 17:10:48 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13122 for ; Fri, 20 Dec 2002 17:10:48 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKMC2v13361; Fri, 20 Dec 2002 17:12:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKMB7v13340 for ; Fri, 20 Dec 2002 17:11:07 -0500 Received: from dmz1.procket.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12989 for ; Fri, 20 Dec 2002 17:07:36 -0500 (EST) Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60]) by dmz1.procket.com (Postfix) with ESMTP id 1218623C4E for ; Fri, 20 Dec 2002 14:07:35 -0800 (PST) Received: from EXCHANGE0-0.na.procket.com (exchange0a.na.procket.com [10.1.7.7]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id gBKMAcie028518 for ; Fri, 20 Dec 2002 14:10:38 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Isis-wg] I-D ACTION:draft-ietf-isis-traffic-04.txt Message-ID: Thread-Topic: [Isis-wg] I-D ACTION:draft-ietf-isis-traffic-04.txt Thread-Index: AcKoI4fT96iue/S9RzSupLt/OVpKMwAUNY2A From: "Tony Li" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gBKMB7v13341 Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 20 Dec 2002 14:10:37 -0800 Content-Transfer-Encoding: 8bit Folks, I'd like to start the WG last call on this document. As there aren't major issues, except that it's been forever, AND counting in the fact that it's the holidays, I'd like to take two weeks. Please comment by 7:00PM PST Jan. 3, 2003. Thanks, Tony | -----Original Message----- | From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] | Sent: Friday, December 20, 2002 4:09 AM | Cc: isis-wg@ietf.org | Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-traffic-04.txt | | | 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 : IS-IS extensions for Traffic Engineering | Author(s) : T. Li, H. Smit | Filename : draft-ietf-isis-traffic-04.txt | Pages : 11 | Date : 2002-12-18 | | This document describes extensions to the IS-IS protocol to support | Traffic Engineering. | This document extends the IS-IS protocol by specifying new | information that an Intermediate System [router] can place in Link | State Protocol Data Units. This information describes additional | details of the state of the network that are useful for traffic | engineering computations. | | A URL for this Internet-Draft is: | http://www.ietf.org/internet-drafts/draft-ietf-isis-traffic-04.txt | | To remove yourself from the IETF Announcement list, send a | message to | ietf-announce-request with the word unsubscribe in the body | of the message. | | 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-traffic-04.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-traffic-04.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 From isis-wg-admin@ietf.org Fri Dec 20 17:57:58 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14477 for ; Fri, 20 Dec 2002 17:57:58 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKMxAv15346; Fri, 20 Dec 2002 17:59:10 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKMwfv15328 for ; Fri, 20 Dec 2002 17:58:41 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14395 for ; Fri, 20 Dec 2002 17:55:09 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1 ident=zinin) by psg.com with esmtp (Exim 3.36 #2) id 18PW5r-000JLx-00 for isis-wg@ietf.org; Fri, 20 Dec 2002 14:58:11 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.51) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <139714747392.20021220145656@psg.com> To: "'isis-wg@ietf.org'" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Isis-wg] IETF/JTC1 Agreement: new ver Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 20 Dec 2002 14:56:56 -0800 Content-Transfer-Encoding: 7bit Guys- The new ver of the agreement incorporating comments from the WG, as well as the wdiff against the -00 version are available for your review: http://psg.com/~zinin/ietf/draft-zinin-ietf-jtc1-aggr-01.txt http://psg.com/~zinin/ietf/draft.wdiff.txt (The draft has been submitted to internet-drafts.) I'm also running this by the JTC1 folks. As soon as I hear back from them, we'll start another IETF LC. As before, we should minimize the changes to the text to avoid another multi-month round within JTC1. Regards. -- Alex _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg