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

<Simo.Veikkolainen@nokia.com> Fri, 22 November 2013 12:34 UTC

Return-Path: <Simo.Veikkolainen@nokia.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 7847C1ADBF7 for <mmusic@ietfa.amsl.com>; Fri, 22 Nov 2013 04:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.726
X-Spam-Level:
X-Spam-Status: No, score=-4.726 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.525, 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 OoHl4gWu2gYv for <mmusic@ietfa.amsl.com>; Fri, 22 Nov 2013 04:34:50 -0800 (PST)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id CF6A21AD9B8 for <mmusic@ietf.org>; Fri, 22 Nov 2013 04:34:49 -0800 (PST)
Received: from smtp.mgd.nokia.com ([65.54.30.24]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id rAMCRJPR021494 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 22 Nov 2013 14:27:20 +0200
Received: from 008-AM1MPN1-024.mgdnok.nokia.com ([169.254.4.50]) by 008-AM1MMR1-008.mgdnok.nokia.com ([65.54.30.24]) with mapi id 14.03.0136.001; Fri, 22 Nov 2013 12:27:19 +0000
From: Simo.Veikkolainen@nokia.com
To: pkyzivat@alum.mit.edu, mmusic@ietf.org
Thread-Topic: [MMUSIC] E164 address type in both RFC 3108 and draft-ietf-mmusic-sdp-cs
Thread-Index: Ac7kg/s/Ox1+oezCTIqy8+w+xBQcogABoWsAALy6IgA=
Date: Fri, 22 Nov 2013 12:27:18 +0000
Message-ID: <D09DAE6B636851459F7575D146EFB54B34E6B843@008-AM1MPN1-024.mgdnok.nokia.com>
References: <7594FB04B1934943A5C02806D1A2204B1C53FE70@ESESSMB209.ericsson.se> <528A59D4.9040504@alum.mit.edu>
In-Reply-To: <528A59D4.9040504@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.21.80.34]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Nokia-AV: Clean
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: Fri, 22 Nov 2013 12:34:52 -0000

Hi,
I'm not actively following the list, but Christer kindly pinged me off-list. For some reason I could not find Christian Groves' email (http://www.ietf.org/mail-archive/web/mmusic/current/msg12771.html)  in my inbox where he writes:

---
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."
---
 
The proposed text sounds good to me as well; we can add it in the next version.

Simo

PS. The RFC number in question is RFC3108, not RFC3105.

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of ext Paul Kyzivat
Sent: 18 November, 2013 20:18
To: mmusic@ietf.org
Subject: Re: [MMUSIC] E164 address type in both RFC 3108 and draft-ietf-mmusic-sdp-cs

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