Re: [MMUSIC] E164 address type in both RFC 3108 and draft-ietf-mmusic-sdp-cs

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 19 November 2013 07:25 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A32B41AC441 for <mmusic@ietfa.amsl.com>; Mon, 18 Nov 2013 23:25:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level:
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9FbKpibF3Mx6 for <mmusic@ietfa.amsl.com>; Mon, 18 Nov 2013 23:25:05 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9715A1AC404 for <mmusic@ietf.org>; Mon, 18 Nov 2013 23:25:04 -0800 (PST)
X-AuditID: c1b4fb2d-b7f1c8e000005ceb-ad-528b1249b6ea
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 26.B7.23787.9421B825; Tue, 19 Nov 2013 08:24:58 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.73]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0328.009; Tue, 19 Nov 2013 08:24:57 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christian Groves <Christian.Groves@nteczone.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] E164 address type in both RFC 3108 and draft-ietf-mmusic-sdp-cs
Thread-Index: AQHO5JDoFWgTp7ouhUKZy3qr7DyTKporkWKAgACWPwA=
Date: Tue, 19 Nov 2013 07:24:56 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C541615@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C53FE70@ESESSMB209.ericsson.se> <528A59D4.9040504@alum.mit.edu> <528AA233.1030005@nteczone.com>
In-Reply-To: <528AA233.1030005@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyM+Jvra6XUHeQwb3N7BZf3jeyWExd/pjF gcljyZKfTB4rzs9kCWCK4rJJSc3JLEst0rdL4Mp4OmkbY8E0iYqXX1YzNjAuF+5i5OSQEDCR uL/gKROELSZx4d56ti5GLg4hgUOMEt1LV7NCOIsZJU7tbWfuYuTgYBOwkOj+pw3SICIQLTFp YTMbiC0sEC5x4l0PG0Q8QmLezz3MELaVxOe/D8DiLAKqErsPrmUCGcMr4Cvx/3QyxPh+Ronf 21aDHcEpoCMxqekrO4jNCHTQ91NrwOLMAuISt57MhzpUQGLJnvPMELaoxMvH/1ghbEWJj6/2 MULU60gs2P2JDcLWlli28DVYPa+AoMTJmU9YJjCKzkIydhaSlllIWmYhaVnAyLKKkT03MTMn vdxwEyMwFg5u+a27g/HUOZFDjNIcLErivB/eOgcJCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRq YLRpWj2DP8xh/U97mxwdk7QFnRGPKtLVe5hP7LgdLxEm/Hiiz4Uedbbibfc2zDZLSBAI3fM9 aKtIQtb3nw6+H+bvemigHz0t88Dsu4FLO74+3M04db2u7eJkQ34taZHP9Wva7I7+1rzJKXie zUXt3Gmd/z98tEIPFv2qNmLfa79E1k1y+8nVDEosxRmJhlrMRcWJAFDMQwVTAgAA
Subject: Re: [MMUSIC] E164 address type in both RFC 3108 and draft-ietf-mmusic-sdp-cs
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 07:25:06 -0000

Hi Christian,

I think your suggestion looks good.

Regards,

Christer

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christian Groves
Sent: 19. marraskuuta 2013 1:27
To: mmusic@ietf.org
Subject: Re: [MMUSIC] E164 address type in both RFC 3108 and draft-ietf-mmusic-sdp-cs

Hello Christer,

I think the last sentence: /"Usage of "E164" address type in conjunction with other network types may be defined elsewhere."/ could potentially be confusing. I think this sentence is referring to that the E164 address defined by [SDP-CS] could be used elsewhere. Whereas the RFC3105 usage of E164 is distinct from [SDP-CS].

I think that after our discussion regarding the IANA registration its clear that Address type is dependent on Network Type. So I would be included to remove the above sentence and just indicate that E164 defined by [SDP-CS] is used exclusively for nettype PSTN.

You could add a note to the effect: "Note: RFC3105 also defines address type E164. This definition is distinct from the one defined by [SDP-CS] and shall not be used with nettype PSTN."


Regards, Christian

On 19/11/2013 5:17 AM, Paul Kyzivat wrote:
> On 11/18/13 9:31 AM, Christer Holmberg wrote:
>> Hi,
>>
>> RFC 3108 (SDP for ATM) defines an 'E164' address type value. When 
>> used, the associated address value is "up to 15 decimal digits".
>>
>> Example: c=ATM E164 9738294382
>>
>> draft-ietf-mmusic-sdp-cs-21 also defines an 'E164' address type 
>> value, with a slightly different syntax for the associated address value:
>>
>> - an international E.164 number (prepended with a '+' sign); or
>> - the value "-", signifying that the address is unknown
>>
>> Now, the sdp-cs draft DOES say:
>>
>>          "Please note that the "E164" address type defined in this 
>> memo is
>>         exclusively defined to be used in conjunction with the "PSTN"
>> network
>>         type in accordance with [RFC4566].  Usage of "E164" address 
>> type in
>>         conjunction with other network types may be defined elsewhere."
>>
>> ...and, in 3108 the network type value is "ATM", so.
>>
>> I just wonder whether it would be useful to, in sdp-cs, give 3108 as 
>> an example of where "E164" is defined for another network type, and 
>> with a different syntax?
>
> I wouldn't object, but neither do I find it necessary to do this.
>
> I wasn't aware of 3108 when it was being standardized. I find its use 
> of "E164" perverted, since it explicitly allows non-E164 values to be 
> used, and doesn't even define how such numbers are to be interpreted.
>
> It should have used something other than "E164". But I guess it is too 
> late to "fix" that.
>
>     Thanks,
>     Paul
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic