Re: [Rserpool] AD comments on draft-ietf-rserpool-enrp-17, draft-ietf-rserpool-asap-17, draft-ietf-rserpool-common-param-13
Magnus Westerlund <magnus.westerlund@ericsson.com> Thu, 22 November 2007 09:42 UTC
Return-path: <rserpool-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iv8aJ-0004zb-0H; Thu, 22 Nov 2007 04:42:59 -0500
Received: from rserpool by megatron.ietf.org with local (Exim 4.43) id 1Iv8aI-0004z5-9W for rserpool-confirm+ok@megatron.ietf.org; Thu, 22 Nov 2007 04:42:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iv8aH-0004y2-Cp for rserpool@ietf.org; Thu, 22 Nov 2007 04:42:57 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iv8aE-00016c-GI for rserpool@ietf.org; Thu, 22 Nov 2007 04:42:57 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 165A02121F; Thu, 22 Nov 2007 10:42:54 +0100 (CET)
X-AuditID: c1b4fb3e-b16a4bb00000459d-a7-47454f1dc662
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id EDCDC21048; Thu, 22 Nov 2007 10:42:53 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Nov 2007 10:42:53 +0100
Received: from [147.214.30.247] ([147.214.30.247]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Nov 2007 10:42:53 +0100
Message-ID: <47454F1D.3060005@ericsson.com>
Date: Thu, 22 Nov 2007 10:42:53 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Rserpool] AD comments on draft-ietf-rserpool-enrp-17, draft-ietf-rserpool-asap-17, draft-ietf-rserpool-common-param-13
References: <4714E8DC.7040000@ericsson.com> <982A2056-1913-46DA-81BF-5B64C091A0F0@lurchi.franken.de> <4743041B.3010304@ericsson.com> <2CA0F3CB-0E8C-4F1E-8F5E-B5D7B7B5E6CD@lurchi.franken.de>
In-Reply-To: <2CA0F3CB-0E8C-4F1E-8F5E-B5D7B7B5E6CD@lurchi.franken.de>
X-Enigmail-Version: 0.95.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Nov 2007 09:42:53.0712 (UTC) FILETIME=[0DE5B100:01C82CEC]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -0.2 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Cc: rserpool@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>, <mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>, <mailto:rserpool-request@ietf.org?subject=subscribe>
Errors-To: rserpool-bounces@ietf.org
Michael Tuexen skrev: >>>> >>>> >>>> A2. Section 7.2: Also what is the security solution for multicast. >>> Not sure what the problem is... The receiver should trust the >>> information >>> in the received multicast message the same way as preconfigured >>> information. >>> It gets an address which might or might no belong to a trustworthy >>> ENRP server. Other mechanisms have t be used for authentication. >> >> Okay, then it maybe should be explicit about that the multicast messages >> are not at all trustworthy. I am also worried that one basically can >> inject a lot of server announcement messages and that way push the valid >> servers into minority so that a client will try all this invalid servers >> and never find a valid one. > That is possible. But using the Multicast messages is completely optional. > They are not secured by IPSec or TLS so you can not trust them... > So what are you expecting here? A sentence or two in the security > considerations > describing the above? Yes, explaining that there is security issues here, but we are not resolving them currently. And that with the exception of the DDOS vector they are any resolved by the later security mechanism. >>>> >>>> A11. Section 6: >>>> >>>> ASAP well known port registration? Is this not needed as the ENRP >>>> protocol will always provide the port? Is that true both for PE and >>>> ENRP? >>> Well, only if multicast is used. In the other case, the well known port >>> is used. >> >> Please include in the IANA section a listing of the well known ports >> that have been assigned. I also think you should include a request to >> update the reference for these ports to this document. > I'm not sure what you want here. If you look at > http://www.iana.org/assignments/port-numbers > and search for asap you will find: > > # Yoshikazu Watanabe <nabe&sm.sony.co.jp> > asap-tcp 3863/tcp asap tcp port > asap-udp 3863/udp asap udp port > # Lyndon Ong <lyong&ciena.com> August 2003 > asap-sctp 3863/sctp asap sctp > # Lyndon Ong <lyong&ciena.com> November 2005 > asap-tcp-tls 3864/tcp asap/tls tcp port > # Lyndon Ong <lyong&ciena.com> August 2003 > asap-sctp-tls 3864/sctp asap-sctp/tls > # Lyndon Ong <lyong&ciena.com> June 2006 > > and for enrp > > enrp 9901/udp enrp server channel > enrp-sctp 9901/sctp enrp server channel > # Lyndon Ong <lyong&ciena.com> June 2006 > enrp-sctp-tls 9902/sctp enrp/tls server channel > # Lyndon Ong <lyong&ciena.com> June 2006 > > If I look at other entries in the document I do not see references > to RFCs. > > So would it be enough to just list these assignments in the IANA section? I would propose that these registrations are transfered over to IETF and having the documents actually being referenced. If you search a bit you will find that some port numbers do have RFC numbers as the reference. So include the list of port numbers in the relevant drafts and then include a request to IANA to update these registrations to point at the documents. I assume Lyndon is fine with this. But he is the current owner of these registrations so he probably needs to notify IANA that he is fine when they actually process the request. > > I guess that we should also list the PPID assignments and request an > update for the reference in > http://www.iana.org/assignments/sctp-parameters > > SCTP Payload Protocol Identifiers Reference > -------------------------------------------------------- --------- > 0 - Reserved by SCTP [RFC4960] > 1 - IUA [RFC4233] > 2 - M2UA [RFC3331] > 3 - M3UA [RFC4666] > 4 - SUA [RFC2960] > 5 - M2PA [RFC2960] > 6 - V5UA [RFC2960] > 7 - H.248 [H.248] > 8 - BICC/Q.2150.3 > [Q.1902.1][Q.2150.3] > 9 - TALI [RFC3094] > 10 - DUA [RFC4129] > 11 - ASAP <draft-ietf-rserpool-asap-03.txt> [Ong] > 12 - ENRP <draft-ietf-rserpool-enrp-03.txt> [Ong] > 13 - H.323 [H.323] > 14 - Q.IPC/Q.2150.3 > [Q.2631.1][Q.2150.3] > 15 - SIMCO <draft-kiesel-midcom-simco-sctp-00.txt> [Kiesel] > 16 - DDP Segment Chunk [RFC5043] > 17 - DDP Stream Session Control [RFC5043] > > Do you agree? >> You shouldn't list all the PPIDs. Only request that IANA updates the ones that are created by the RSERPOOL documents to point at the RSERPOOL documents. Cheers Magnus Westerlund IETF Transport Area Director & TSVWG Chair ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM/M ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool
- [Rserpool] AD comments on draft-ietf-rserpool-enr… Magnus Westerlund
- RE: [Rserpool] AD comments on draft-ietf-rserpool… Ong, Lyndon
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Magnus Westerlund
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Michael Tuexen
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Michael Tuexen
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Magnus Westerlund
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Magnus Westerlund
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Michael Tuexen
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Michael Tuexen
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Magnus Westerlund
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Magnus Westerlund
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Magnus Westerlund
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Magnus Westerlund
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Magnus Westerlund
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Qiaobing Xie
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Magnus Westerlund
- Re: [Rserpool] AD comments on draft-ietf-rserpool… Ong, Lyndon