From extest-admin@lists.bell-labs.com Thu May 1 04:58:23 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02759 for ; Thu, 1 May 2003 04:58:08 -0400 (EDT) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h4190jR29500 for ; Thu, 1 May 2003 05:00:45 -0400 Date: Thu, 1 May 2003 05:00:45 -0400 Message-Id: <200305010900.h4190jR29500@share.research.bell-labs.com> Subject: lists.bell-labs.com mailing list memberships reminder From: mailman-owner@lists.bell-labs.com To: ipo-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: extest-admin@lists.bell-labs.com Errors-To: extest-admin@lists.bell-labs.com X-BeenThere: extest@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk This is a reminder, sent out once a month, about your lists.bell-labs.com mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, ip-optical-request@lists.bell-labs.com) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@lists.bell-labs.com. Thanks! Passwords for ipo-archive@lists.ietf.org: List Password // URL ---- -------- ip-optical@lists.bell-labs.com archive http://lists.bell-labs.com/mailman/options/ip-optical/ipo-archive%40lists.ietf.org From ip-optical-admin@lists.bell-labs.com Fri May 9 10:00:54 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16126 for ; Fri, 9 May 2003 10:00:54 -0400 (EDT) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h49E1rR14405; Fri, 9 May 2003 10:01:53 -0400 Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h49DwHR14377 for ; Fri, 9 May 2003 09:58:17 -0400 Received: from lists.bell-labs.com (H-135-104-27-211.research.bell-labs.com [135.104.27.211]) by crufty.research.bell-labs.com (8.12.9/8.12.9) with ESMTP id h49Dw29Y007600 for ; Fri, 9 May 2003 09:58:02 -0400 (EDT) Received: by lists.bell-labs.com (Postfix) id 57936443A5; Fri, 9 May 2003 09:57:57 -0400 (EDT) Delivered-To: ip-optical@sunny.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.bell-labs.com (Postfix) with ESMTP id 315FA443A4 for ; Fri, 9 May 2003 09:57:57 -0400 (EDT) Received: from dusty.research.bell-labs.com (dusty.research.bell-labs.com [135.104.2.7]) by scummy.research.bell-labs.com (8.12.9/8.12.9) with ESMTP id h49DvtUf023616 for ; Fri, 9 May 2003 09:57:55 -0400 (EDT) Received: from mta1.wss.scd.yahoo.com (mta1.wss.scd.yahoo.com [66.218.85.32]) by dusty.research.bell-labs.com (8.12.9/8.12.9) with ESMTP id h49DuREQ075021 for ; Fri, 9 May 2003 09:56:27 -0400 (EDT) Received: from AwducheHPlapt (68.100.145.226) by mta1.wss.scd.yahoo.com (7.0.015.1) (authenticated as awduche@awduche.com) id 3EBA91C1000C007A for ip-optical@lists.bell-labs.com; Fri, 9 May 2003 06:57:48 -0700 Reply-To: From: "Daniel O. Awduche" To: Message-ID: <002301c31632$f0b7f770$e2916444@awduche.com> 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, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Subject: [IP-Optical] FW: IESG feedback on draft-ietf-ipo-framework Sender: ip-optical-admin@lists.bell-labs.com Errors-To: ip-optical-admin@lists.bell-labs.com X-BeenThere: ip-optical@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Fri, 9 May 2003 09:57:32 -0400 Content-Transfer-Encoding: 7bit Fyi -----Original Message----- From: Alex Zinin [mailto:zinin@psg.com] Sent: Thursday, May 08, 2003 1:00 PM To: Daniel O . Awduche Cc: Wijnen, Bert (Bert) Subject: IESG feedback on draft-ietf-ipo-framework Daniel- The IESG considered the document at the telechat last week and tentatively approved it subject to addressing of the concerns below (these are the last set of comments from the IESG, sorry we had to come back to you more than once, normally we try to bring all comments together first time.) I will put these into the ID tracker, so the comments are publicly visible. Also, feel free to forward this to the WG. Hopefully we can have the next (and last) rev out soon and will push it to the rfc-ed. Cheers. Alex Administrative: We should check with ITU and T1X1 folk if they are fine with this document, since there is L1 stuff in it. Please follow up with Steve Trowbridge and Deborah Brungard(dbrungard@att.com). Security: Section 9.1 says: 1. Replay protection, which detects and rejects attempts to reorder, duplicate, truncate, or otherwise tamper with the proper sequence of messages, and This is not quite right. Replay mechanisms do not provide connection-oriented data integrity. Replay mechanisms allow reorder within a window, and truncation protection is not provided. Section 9.1 also says: 2. Non-repudiation, which may be desirable for accounting and billing purposes. Non-repudiation is an application layer security service. I am surprised to see it in this document. Routing (section 5.2.2.1) Please add some text considering the following potential negative effects: o amount of information that optical nodes will have to maintain will not be bound by the size of the optical network anymore, but will have to include external routes too o stability of the optical network's control plane system will not be solely driven by the dynamics within the optical network itself, but also by the dynamics within the external routing domains where external reachability information is received from. Restoration part: the following text is terse: With out-of-band control, it is necessary to consider fast signaling over the control channel using very short IP packets and prioritized processing. While it is possible to use RSVP or CR- LDP for activating protection paths, these protocols do not provide any means to give priority to restoration signaling as opposed to signaling for provisioning. For instance, it is possible for a restoration-related RSVP message to be queued behind a number of provisioning messages thereby delaying restoration. It is therefore necessary to develop a definition of QoS for restoration signaling and incorporate mechanisms in existing signaling protocols to achieve this. Or, a new signaling protocol may be developed exclusively for activating protection paths during restoration. The last two sentences are a very brief reference to what would be a significant piece of work that needs more justification and a sharper (not detailed, but more specific, multi-sentence) characterization. Would the QoS term be a reference to be a new priority service for RSVP-TE? Where/how would this work be developed? It would do better service to the framework to briefly describe where the fast restoration directions have gone (and explain their rationale a bit), and what would be the characteristics of the new signalling protocol that might be needed. ID-NITs: -: 1 lines containing non-US-ASCII characters -: 42 lines longer than 72 characters, max 369 Figure 1 is messed up. For example, one of the lines is 370 characters long. _______________________________________________ IP-Optical mailing list IP-Optical@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/ip-optical