[NSIS] IETF 55 Meeting Minutes
john.loughney@nokia.com Tue, 03 December 2002 19:55 UTC
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 OAA13443 for <nsis-archive@odin.ietf.org>; Tue, 3 Dec 2002 14:55:12 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gB3Jva909573 for nsis-archive@odin.ietf.org; Tue, 3 Dec 2002 14:57:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB3JvVv09566; Tue, 3 Dec 2002 14:57:31 -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 gB3JuQv09499 for <nsis@optimus.ietf.org>; Tue, 3 Dec 2002 14:56:26 -0500
Received: from mgw-x4.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13390 for <nsis@ietf.org>; Tue, 3 Dec 2002 14:53:30 -0500 (EST)
From: john.loughney@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id gB3JvRW03515 for <nsis@ietf.org>; Tue, 3 Dec 2002 21:57:27 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5ef2cf0023ac158f2431a@esvir04nok.ntc.nokia.com> for <nsis@ietf.org>; Tue, 3 Dec 2002 21:56:18 +0200
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 3 Dec 2002 21:56:17 +0200
Received: from esebe014.NOE.Nokia.com ([172.21.138.53]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 3 Dec 2002 21:56:17 +0200
Received: from esebe022.NOE.Nokia.com ([172.21.138.113]) by esebe014.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 3 Dec 2002 21:56:17 +0200
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"
Date: Tue, 03 Dec 2002 21:56:17 +0200
Message-ID: <A16A3EE4D4CA124FADC7987B1AC89FE41F2713@esebe022.ntc.nokia.com>
Thread-Topic: What is the goal of the analysis draft?
Thread-Index: AcKa4NZ1SRcmd4n8RNe2bve/2p8lyQACR29wAAbzveA=
To: nsis@ietf.org
X-OriginalArrivalTime: 03 Dec 2002 19:56:17.0661 (UTC) FILETIME=[0B0262D0:01C29B06]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gB3JuQv09500
Subject: [NSIS] IETF 55 Meeting Minutes
Sender: nsis-admin@ietf.org
Errors-To: nsis-admin@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Hi all, Here is the first version of the minutes from IETF 55. I still need to do a good proof-read. Comments welcome. Thanks, John The NSIS working group met twice at IETF 55 NSIS Tuesday, November 19, 1300-1400 Afternoon Session I ================================================= WG Status, charter discussion - chair http://www-nrc.nokia.com/sua/nsis/ietf55/charter.txt The chair went over the main highlights of the charter. IP signaling protocol with QoS as first use case is the main goal, focusing on a two-layer signaling approach. Existing work will be completed. Developing transport layer signaling for transport of upper layer signaling with an initial application layer will be optimized RSVP. A potential for a second layer will be in consultation with ADs (to ensure the solution developed is not QoS specific. Comments were raised regarding the justification for the design of a new protocol. It was noted that even though there may be specific problems with RSVP the work does not seem to depend on the analysis. Scoping problems regarding the previous charter were noted. It was asked whether Transport Signaling Layer referred to OSI layer 4. It was explained that this was not the case and that there was a precedent for using the term transport, such as TLS. Security is not an explicit goal and the intention is to reuse existing securi! ty mechanisms. The applicability of current framework is kept. It was mentioned that it is a non-goal to define what QoS is. Cross-realm policy needs to be solved. Authentication and Authorization requirements for application layer are going to be different from transport layer. They should be considered on a case-by-case basis. A comment was made that a reliable solution for NAT/firewall traversal is needed. The area director pointed out that NSIS may need to work on SIP change for RSVP. Pulling in loose ends from SIP. Needs to be made coherent. Next steps are to take charter to list, review by IESG afterwards. Like to get feedback. Terminology Discussion - Robert Hancock - (10 min) http://www-nrc.nokia.com/sua/nsis/ietf55/NSIS-Terminology-Issues.ppt Robert Hancock clarified that the goal of the contribution is to provide unambiguous, unsurprising terms that can usefully describe the NSIS problem space. Non-traditional routing was discussing. Conclusion was that 'Policy forwarding' seems to be the consensus. Path-(de)coupled was discussed and decided to be used. A name for the thing signaling is requesting or installing. Proposals included 'reservation', 'RMF'. Conclusion was that this needs discussion on the mailing list. Working Group and protocol names such as NTLP/NSLP. It was stated that these are not proposed names for protocols but anything using 'NSIS' is placeholder until we begin the protocol. It was decided to use 'peer' not neighbor. Should always use discovery qualified as 'peer discovery', 'topology discovery', 'path discovery.' Sender/receiver initiation/orientation needs further discussion on the mailing list. Requirements - Marcus Brunner http://www.ietf.org/internet-drafts/draft-ietf-nsis-req-05.txt http://www-nrc.nokia.com/sua/nsis/ietf55/IETF55_Req.ppt Marcus discussed changes from version 04, such as trying to get rid of QoS unless used as example. Five major open issues remain. Two requirements for local information exchange, 5.3.5 separate messages & 5.4.2 information piggybacking. The proposal is to keep both but clarify the text. It felt that things that are state-related should have independent identifier. Replay protection was agreed as a MUST requirement. Confidentiality of signaling issues was discussed, with a comment that this requirement may be dependent upon which layer is being discussed. WEDNESDAY, November 20, 2002 0900-1130 Morning Session ================================================= Next Steps in Signaling: Framework - Robert Hancock http://www.ietf.org/internet-drafts/draft-ietf-nsis-fw-00.txt http://www-nrc.nokia.com/sua/nsis/ietf55/NSIS-framework-issues.ppt The division between NTLP and NSLP was discussed on the following points. Message types: The question is not to define any message formats here, but it is more about message sequences and message flows. Flow issues: There were slight concerns to have policy routing (forwarding) mentioned in the presentation, but it was clarified that we are not defining policy forwarding in this WG. Path management: It was asked and clarified that NTLP layer is not doing any kind of stream management. The correlation between the layers is a difficult question and reservation ID issue is addressed in another slide. Security issues: We are protecting signaling and signaling messages. Security needs to be clarified when the scope of transportation layer is clear. State management: Different views were presented on whether the state management should be taken care by NTLP layer or not. The work will continue with the issues introduced in the presentation and comments are to be sent to the mailin! g list. Trade-offs and open issues with path discovery and transport - Henning Schulzrinne http://www.ietf.org/internet-drafts/draft-schulzrinne-nsis-casp-00.txt http://www-nrc.nokia.com/sua/nsis/ietf55/55-NSIS.ppt Next hop discovery and routing functionality was questioned on this proposal. Concern was raised that features showed in the presentation are not common for all use case. At this phase it was proposed transport layer to be more general. In general next node discovery raised many concerns and questions and more discussion is needed in the list. A Two-Level Architecture for Internet Signaling - chair http://www.ietf.org/internet-drafts/draft-braden-2level-signaling-01.txt http://www-nrc.nokia.com/sua/nsis/ietf55/2level.atlanta.ppt John Loughney gave the presentation instead of the authors. It was questioned that is the soft state necessary functionality for the transport layer. It was asked how much of previous presentation as well as this presentation is covered already in the framework documents. We should discuss in this group, what parts should be covered in the framework. It was pointed out in the session that it is not appropriate way to base the architecture and framework work for some existing protocol as RSVPv1 is used now. Several points needs to be clarified in the mailing list, since the author of the draft was not at present in the session. Also some hesitation was raised against the planned re-engineering of the signaling framework. Sender and Receiver Orientation Issues in NSIS - Robert Hancock http://www.ietf.org/internet-drafts/draft-hancock-nsis-sender-receiver-00.txt http://www-nrc.Nokia.com/sua/nsis/ietf55/NSIS-Sender-Receiver-Issues.ppt The directionality is not so relevant for the transport layer, but it is more related to the reservations. Analysis of Existing Quality of Service Signaling Protocols - Jukka Manner http://www.ietf.org/internet-drafts/draft-ietf-nsis-signalling-analysis-00.txt http://www-nrc.nokia.com/sua/nsis/ietf55/analysis.pdf It was asked to send the text/information about the possible other signaling protocols to the authors of this document. Security issues are not going to be covered in this document. Robustness of different solutions was seen to be one issue to be studied in this document. Scalability was seen difficult issue to be captured in the document, but some text proposal may be sent to the mailing list on that topic. NSIS Threats - H. Tschofenig http://www.ietf.org/internet-drafts/draft-ietf-nsis-threats-00.txt http://www-nrc.nokia.com/sua/nsis/ietf55/Security-Signaling.ppt Divergent view was presented on relationship between the flow identifier and security. Security AD had big concerns with the authorization and NSIS signaling. He mentioned it is very hard to implement hop-by-hop security. Figuring the authorization is an essential challenge for this WG. The security issues for NSIS WG are similar than SIP WG has. Authorization made by hop-by-hop is probably an unsolvable problem, but we should consider authorization issue as more of an upper layer issue. RSVP Security Properties - H. Tschofenig http://www.ietf.org/internet-drafts/draft-ietf-nsis-rsvp-sec-properties-00.txt http://www-nrc.nokia.com/sua/nsis/ietf55/RSVP-Security-Properties.ppt Feedback is needed for this. It was asked that have we considered using group keys, but we haven't. In general the problems with keys and end-to-middle authentication would be good to describe in the document. Analysis of Existing QoS Solutions - G. Karagiannis http://www.ietf.org/internet-drafts/draft-demeer-nsis-analysis-03.txt http://www-nrc.nokia.com/sua/nsis/ietf55/IETF55-Analysis-karagiannis-02.ppt Authors should align the analyses together with the authors of the NSIS WG signaling document. Analysis of Mobile IP and RSVP Interactions - Mike Thomas - (10 minutes) http://www.ietf.org/internet-drafts/draft-thomas-nsis-rsvp-analysis-00.txt http://www-nrc.nokia.com/sua/nsis/ietf55/ This is two years old draft, which is now resurrected. In practice this could be a working group document or then this analyze could be captured in the NSIS analyses document including conclusions. There was not time to discuss the following drafts: A Proposal for RSVPv2 - Karagiannis http://www.ietf.org/internet-drafts/draft-westberg-proposal-for-rsvpv2-01.txt http://www-nrc.nokia.com/sua/nsis/ietf55/IETF55-RSVPv2-karagiannis-01.ppt A Firewall/NAT Traversal Client for CASP - H. Tschofenig http://www.ietf.org/internet-drafts/draft-tschofenig-nsis-casp-midcom-00.txt http://www-nrc.nokia.com/sua/nsis/ietf55/Implications-Relationships-NSIS.ppt The Use of Bi-Directional RSVP in the Wireless Internet - Kamel Shaheen http://www.ietf.org/internet-drafts/draft-Shaheen-shahrier-nsis-brsvp-00.txt http://www-nrc.nokia.com/sua/nsis/ietf55/B-RSVP.ppt Signaling Interworking for IPv6 Network - Gyu Myoung Lee http://www.ietf.org/internet-drafts/draft-choi-ipv6-signaling-interworking-00.txt http://www-nrc.nokia.com/sua/nsis/ietf55/draft-choi-ipv6-signaling-interworking-00.ppt _______________________________________________ nsis mailing list nsis@ietf.org https://www1.ietf.org/mailman/listinfo/nsis
- [NSIS] IETF 55 Meeting Minutes john.loughney
- RE: [NSIS] IETF 55 Meeting Minutes john.loughney