[MMUSIC] E.164 and visual separators in draft-ietf-mmusic-sdp-cs

<Simo.Veikkolainen@nokia.com> Thu, 15 November 2012 09:06 UTC

Return-Path: <Simo.Veikkolainen@nokia.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA7421F86A6 for <mmusic@ietfa.amsl.com>; Thu, 15 Nov 2012 01:06:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c9g9Q8hK4ixV for <mmusic@ietfa.amsl.com>; Thu, 15 Nov 2012 01:06:15 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id E74F421F87EA for <mmusic@ietf.org>; Thu, 15 Nov 2012 01:06:14 -0800 (PST)
Received: from vaebh106.NOE.Nokia.com (in-mx.nokia.com [10.160.244.32]) by mgw-da02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id qAF963wE023156; Thu, 15 Nov 2012 11:06:04 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.20]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 15 Nov 2012 11:06:02 +0200
Received: from 008-AM1MPN1-025.mgdnok.nokia.com ([169.254.5.80]) by 008-AM1MMR1-011.mgdnok.nokia.com ([65.54.30.20]) with mapi id 14.02.0318.003; Thu, 15 Nov 2012 09:06:02 +0000
From: Simo.Veikkolainen@nokia.com
To: mmusic@ietf.org, fandreas@cisco.com, pkyzivat@alum.mit.edu, keith.drage@ALCATEL-LUCENT.COM
Thread-Topic: E.164 and visual separators in draft-ietf-mmusic-sdp-cs
Thread-Index: Ac3DEGXfrPAdBGk/TW6QWq/Xh+eM1g==
Date: Thu, 15 Nov 2012 09:06:01 +0000
Message-ID: <D09DAE6B636851459F7575D146EFB54B1A3BD4C3@008-AM1MPN1-025.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-titus-version: 3.3.8.1
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Nokia Internal Use Only; Project=None;
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: XyNKkw7TEHXS2OcfARBaXWR9O9Mb2ID5/iXRFxlBB1rANS5f/I/LxLjD3bRObMSFWt+RqxPiPwAO+YD8Q2XFOzWn95d+5/rAglLPu0gFYk4UNtR6h+x+VmJ2NB4oQbKrQJo3UusHiCWmNRe2tLy9iNwp962GlwdFAawRcn9tKeu034CLiby85ct1rhN/+Be0bg4MTcDIDlbPmqL+0Usi5n/AgMch64TCTw48cn3iu2reAGOzQ4pxwTrtNbiRLc5bPSyf8tSeabVERRKBVTxwuw==
x-originating-ip: [10.236.8.80]
Content-Type: multipart/alternative; boundary="_000_D09DAE6B636851459F7575D146EFB54B1A3BD4C3008AM1MPN1025mg_"
MIME-Version: 1.0
X-OriginalArrivalTime: 15 Nov 2012 09:06:02.0856 (UTC) FILETIME=[6FF0D680:01CDC310]
X-Nokia-AV: Clean
Subject: [MMUSIC] E.164 and visual separators in draft-ietf-mmusic-sdp-cs
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 15 Nov 2012 09:06:18 -0000

Hi Flemming, Paul, Keith, and all,

When going through http://tools.ietf.org/id/draft-ietf-mmusic-sdp-cs-13.txt for publication, Flemming had a comment on the format of global telephone numbers.

The draft currently says in Section 5.2.1:

  This memo exclusively uses the international representation of E.164
   numbers, i.e., those initiated with a '+' sign.  The syntax (see
   Section 5.7) refers to the representation of a 'global-number'
   construction already specified in RFC 3966 [RFC3966].  This
   representation requires the presence of the '+' sign.  Additionally,
   this representation allows for the presence of one or more 'visual-
   separator' constructions.  Implementations confirming to this
   specification and using the "E164" address type together with the
   "PSTN" network type MUST only use international E.164, i.e., those
   starting with a '+' sign and SHOULD NOT use visual-separators.

This was discussed earlier on the list, see  http://www.ietf.org/mail-archive/web/mmusic/current/msg09630.html

Flemming's comment was that referencing to RFC3966 but saying that the syntax is invalid because we only use parts of it is not a good idea.

The question is, could we just refer to RFC3966 and allow visual separators?

In my understanding the tradeoff is between slightly increased complexity in parser implementation versus being clear on the syntax. I would be inclined to prefer the latter.

Regards,
Simo