Re: [Enum] Review of draft-yu-enumservice-sms-smpp
"Richard Shockey" <richard@shockey.us> Thu, 24 April 2008 22:58 UTC
Return-Path: <enum-bounces@ietf.org>
X-Original-To: enum-archive@megatron.ietf.org
Delivered-To: ietfarch-enum-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 138A13A6B35; Thu, 24 Apr 2008 15:58:16 -0700 (PDT)
X-Original-To: enum@core3.amsl.com
Delivered-To: enum@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F3293A6B35 for <enum@core3.amsl.com>; Thu, 24 Apr 2008 15:58:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level:
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JrM3IciZV2N3 for <enum@core3.amsl.com>; Thu, 24 Apr 2008 15:58:13 -0700 (PDT)
Received: from mail.songbird.com (mail.songbird.com [208.184.79.10]) by core3.amsl.com (Postfix) with ESMTP id 8E0223A6946 for <enum@ietf.org>; Thu, 24 Apr 2008 15:58:13 -0700 (PDT)
Received: from rshockeyPC (h-68-165-240-38.mclnva23.covad.net [68.165.240.38]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id m3OMuslp021024 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 24 Apr 2008 15:56:57 -0700
From: Richard Shockey <richard@shockey.us>
To: 'Alexander Mayrhofer' <alexander.mayrhofer@enum.at>, james.yu@neustar.biz, enum@ietf.org
References: <480F5861.3050006@enum.at>
In-Reply-To: <480F5861.3050006@enum.at>
Date: Thu, 24 Apr 2008 18:57:40 -0400
Message-ID: <005a01c8a65e$9c799710$d56cc530$@us>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcilWD49o8dwtwq+RUClPQYgHtpCFgBBi+nw
Content-Language: en-us
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: richard@shockey.us
Cc: paf@cisco.com
Subject: Re: [Enum] Review of draft-yu-enumservice-sms-smpp
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: enum-bounces@ietf.org
Errors-To: enum-bounces@ietf.org
So I'm assuming for purposes of argument that there is no objection to making this a WG document. > -----Original Message----- > From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf > Of Alexander Mayrhofer > Sent: Wednesday, April 23, 2008 11:40 AM > To: james.yu@neustar.biz; enum@ietf.org > Subject: [Enum] Review of draft-yu-enumservice-sms-smpp > > > Hello Yu, > > i spent some time on reviewing your sms:smpp draft - i have a couple > of > comments (i probably missed some details, but given the early stage of > the draft, i guess we'll go through more reviewing anyway..) > > I like the idea, i understand that it makes sense. However, i don't > think this is neccessarily limited to private use... For example, > we're > running our own SMPP server for the number range +4359966, and i don't > see why i wouldn't publish a corresponding ENUM record even in User > ENUM > ... (we're limiting access on the SMPP layer, of course). > > There are some minor things, but also some major content issues, i've > listed them in the order i noticed them... > > > - Title: I'd recommend moving the "RFC 4355" part to the block on top > of > the draft, so that it says "Updates: RFC 4355 (if approved)". I'd also > change the title into "IANA registration of the 'smpp' URI scheme and > the 'smpp' subtype for the 'sms' Enumservice" (or the other way round, > mentioning the Enumservice first) > > - The draft does not have proper page breaks. > > - Maybe you could merge "Conventions" and "Abbreviations" into a > "Terminology" section, and put it in front of the Introdcution, which > would save you expanding all the terms in the intro. > > - There should be an informative reference to X.25 > > - The ABNF reference is outdated in the text (2234), but ok in the > references (RFC 5234) > > - Section 5 ("use of..") is not just about the URI scheme, also about > the Enumservice. Maybe just rename that to "Use Cases" or "Use Case > Examples". Disclaimer: I didn't go thorugh the use cases themselves > because i'm not that deep into SMS delivery :-) > > - I'm missing a description of the dereference process of an "smpp" > URI. > For example: What is the exact process of determining the final (IP > level) destination (and port) from an "hostpart": > > - Does it make use of NAPTR lookups, or SRV lookups? > - What is the default port, if not defined? > - How can one specify a port? in the "hostpart"? > > The "hostpart" that you say is "imported from RFC 3261" is not > specified > in 3261... it occurs once in the text, but is never specified... > > In addition, the "telephone-subscriber" that you import into the > "user" > part already allows parameters (namely, all "tel" URI parameters, so > you > do essentially allow _two_ sets of parameters, like > > smpp:+4359966;cic=+1-6789;npdi@smpp.example.com;parameterXY=bla > > Does that make sense, and is this intended? If it is intended, what > are > the semantics of the "user" parameters... I'm unsure whether this is > actually allowed by the URI ABNF itself... > > - Would it be possible to make note of the "Application Class" subtype > in the Enumservice Registration itself? i think it would be a "Common > Application" Enumservice as in 4.2.4 of the Enumservice guide draft.. > > - The column (":") is not part of the URI scheme name. Please remove > it > from the URI scheme part of the registration template. > > - I'm not happy with the last sentence of the "security > considerations" > section of the Enumservice template (limiting access to the DNS). I > think that might also trigger a lot of headwind from the DNS guys. > It's > actually an implementation veriant in certain scenarios, but i don't > see > why that would need to be included in the registration template. > > - The URI scheme needs improvement. As mentioned above, i can't find > the > "hostpart" definition, the "telephone-subscriber" import adds > parameter > space with unclear semantics, and i'm missing clear dereferencing > instructions. > > - If you define parameters for the SMPP URI, you will probably need to > define a registry for them (remember what happened to the tel: URI - > they needed to add a registry in a seperate document > http://www.ietf.org/internet-drafts/draft-ietf-iptel-tel-reg-05.txt) > > - References: I think a couple of references can be moved to > informative > status. > > hope that helps! > > cheers > > Alex > _______________________________________________ > enum mailing list > enum@ietf.org > https://www.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www.ietf.org/mailman/listinfo/enum
- [Enum] Review of draft-yu-enumservice-sms-smpp Alexander Mayrhofer
- Re: [Enum] Review of draft-yu-enumservice-sms-smpp Richard Shockey
- Re: [Enum] Review of draft-yu-enumservice-sms-smp… Richard Shockey
- Re: [Enum] Review of draft-yu-enumservice-sms-smp… Peter Koch
- Re: [Enum] Review of draft-yu-enumservice-sms-smp… Richard Shockey
- Re: [Enum] Review of draft-yu-enumservice-sms-smp… lconroy
- Re: [Enum] Review of draft-yu-enumservice-sms-smp… Richard Shockey
- Re: [Enum] Review of draft-yu-enumservice-sms-smp… Bernie Hoeneisen
- Re: [Enum] Review of draft-yu-enumservice-sms-smpp Yu, James
- Re: [Enum] Review of draft-yu-enumservice-sms-smp… Bernie Hoeneisen
- [Enum] Scheduling Enum WG meeting Dublin (was Re:… Bernie Hoeneisen
- Re: [Enum] Scheduling Enum WG meeting Dublin (was… Richard Shockey