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

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 18 November 2013 18:38 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 C67FD1A1F4B for <mmusic@ietfa.amsl.com>; Mon, 18 Nov 2013 10:38:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.972
X-Spam-Level:
X-Spam-Status: No, score=0.972 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.972] autolearn=no
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 KUpWpNNbotWL for <mmusic@ietfa.amsl.com>; Mon, 18 Nov 2013 10:38:47 -0800 (PST)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id BC46F1A1F48 for <mmusic@ietf.org>; Mon, 18 Nov 2013 10:38:46 -0800 (PST)
Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta13.westchester.pa.mail.comcast.net with comcast id r0mv1m00816LCl05D6HwQp; Mon, 18 Nov 2013 18:17:56 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta06.westchester.pa.mail.comcast.net with comcast id r6Hw1m00S3ZTu2S3S6HwUX; Mon, 18 Nov 2013 18:17:56 +0000
Message-ID: <528A59D4.9040504@alum.mit.edu>
Date: Mon, 18 Nov 2013 10:17:56 -0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C53FE70@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C53FE70@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1384798676; bh=VSk9oU659fMe1A6/AOHKTDQBS9gPzwYZi/43GCnGN5I=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=QZ8qEccplxanjxig49f3tt5OdypK8i2fdqD4uY+dXAY+/9Q0uTF1dxABrCrsvGKkF 2WfjcGEsDy5UagfjQWdAELZow2KKFd572F3cTWIDocyiU3IMGMSm3XBg28+S3I1nqg SHTdDXnRx2hH8WYc4wncGIxYBGt9yZpTYgU+ake+tHE4m+41PH9bhFi3qru1nLZOIl W46rcW5H27xjEEMq13fU9K1+r4sdS5j8q0f9hQpIiMAzs5T9hKnp3P5fkpyzNxTK+n WCVkGRLIyI6Uf6axrE6fl70QU/fCwpt9uzZyqIfpxms05EGvJCXvGxN6IVXY9CzDEw PIYZSOZItXs7A==
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: Mon, 18 Nov 2013 18:38:48 -0000

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