Re: [Dime] WGLC for draft-ietf-dime-extended-naptr

Mark Jones <mark@azu.ca> Mon, 10 January 2011 20:10 UTC

Return-Path: <mark@azu.ca>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12B2128C0E5 for <dime@core3.amsl.com>; Mon, 10 Jan 2011 12:10:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.727
X-Spam-Level:
X-Spam-Status: No, score=-2.727 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 79m5WuVzagmI for <dime@core3.amsl.com>; Mon, 10 Jan 2011 12:10:48 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 096EF28C0F9 for <dime@ietf.org>; Mon, 10 Jan 2011 12:10:46 -0800 (PST)
Received: by qwi2 with SMTP id 2so4472163qwi.31 for <dime@ietf.org>; Mon, 10 Jan 2011 12:13:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.85.207 with SMTP id p15mr2863516qcl.167.1294690380785; Mon, 10 Jan 2011 12:13:00 -0800 (PST)
Received: by 10.229.219.197 with HTTP; Mon, 10 Jan 2011 12:13:00 -0800 (PST)
In-Reply-To: <002301cbaf10$81bee520$853caf60$@net>
References: <20110106191502.10151.87573.idtracker@localhost> <AANLkTi=3TduoqU2Ufcp=diAE=BwvX1KutNQXmX5r5aRa@mail.gmail.com> <EB0843F7-A291-439C-8F20-1F6993576B07@gmail.com> <002301cbaf10$81bee520$853caf60$@net>
Date: Mon, 10 Jan 2011 15:13:00 -0500
Message-ID: <AANLkTi=hEPvW0YAUt5h8JdTZQspqrz89RtnMvWqZHjyM@mail.gmail.com>
From: Mark Jones <mark@azu.ca>
To: Glen Zorn <gwz@net-zen.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: dime@ietf.org
Subject: Re: [Dime] WGLC for draft-ietf-dime-extended-naptr
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2011 20:10:53 -0000

Hi Glen,

Thanks for the review.

On Sat, Jan 8, 2011 at 3:46 AM, Glen Zorn <gwz@net-zen.net> wrote:
>
> Would somebody tell me again why we're issuing an update for a document that
> will be obsolete very soon?
>

I direct your attention to the "can of worms" presentation from IETF#76. :)

http://www.ietf.org/proceedings/77/slides/dime-5.pdf

At the time we started this draft, it was uncertain whether 3588bis
would beat it to publication. So we decided to proceed optimistically
assuming the SNAPTR draft would get published first with the
understanding that we'd have some updates to do if we were wrong.

The application-neutral aspects of SNAPTR (e.g "aaa:diameter.sctp")
were also contributed to 3588bis to ensure that 3588bis would be
functionally complete if it got published first and this draft would
come along later to add the application-specific SNAPTR entries (e.g.
"aaa+ap5:diameter.sctp").

>
> This draft appears to be in some conflict w/rfc3588bis; in particular, both
> request that IANA register the same set of S-NAPTR Application Protocol
> Tags.
>
> This draft updates RFC 3588 but says nothing about 3588bis; 3588bis says
> nothing about this document.  This seems to lead to a dead-end.
>

If 3588bis is published first, we will need to change this draft to
state that it updates 3588bis instead of 3588 and remove the duplicate
SNAPTR protocol tag entries.

> This draft is considerably more detailed WRT S-NAPTR than 3588bis.  Why?
>

This draft includes the level of detail required to satisfy the
reviewers. The extra detail may be explained by the
application-specific S-NAPTR grammar/usage being slightly more
complicated than the application-neutral one in 3588bis. Do you think
some essential details are missing from the 3588bis procedures?

Regards
Mark

> Hope this helps.
>
>  ~gwz
>
> > -----Original Message-----
> > From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of
> > Jouni
> > Sent: Saturday, January 08, 2011 5:51 AM
> > To: dime@ietf.org
> > Cc: dime-chairs@tools.ietf.org
> > Subject: [Dime] WGLC for draft-ietf-dime-extended-naptr
> >
> > Folks,
> >
> > We will rerun a short WGLC for draft-ietf-dime-extended-naptr-04 since
> > there were some bigger restructuring on the document. The WGLC starts as
> > of today 8th Jan 2011 and ends 14th Jan 2011 23:59 CET+1. If you have
> > substantial technical comments, please post them to the list. Purely
> > editorial comments can be mailed directly to the authors. Silence will
> > be taken as acceptance.
> >
> > - Jouni (as a Dime co-chair)
> >
> >
> > _______________________________________________
> > DiME mailing list
> > DiME@ietf.org
> > https://www.ietf.org/mailman/listinfo/dime
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime