Re: [port-srv-reg] Fwd: draft-ietf-tsvwg-iana-ports-07

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 22 October 2010 12:12 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: port-srv-reg@core3.amsl.com
Delivered-To: port-srv-reg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34D653A6900 for <port-srv-reg@core3.amsl.com>; Fri, 22 Oct 2010 05:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.624
X-Spam-Level:
X-Spam-Status: No, score=-102.624 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 3En-EXqY-b9Z for <port-srv-reg@core3.amsl.com>; Fri, 22 Oct 2010 05:12:33 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id AF0923A68E0 for <port-srv-reg@ietf.org>; Fri, 22 Oct 2010 05:12:32 -0700 (PDT)
Received: from [172.16.2.124] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TMGAEQAEeUxy@rufus.isode.com>; Fri, 22 Oct 2010 13:14:09 +0100
Message-ID: <4CC18002.5080103@isode.com>
Date: Fri, 22 Oct 2010 13:13:54 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Olafur Gudmundsson <ogud@ogud.com>
References: <201010220019.CAA27355@TR-Sys.de> <AD37D1C4-9844-42A7-8900-895FC8CD3BDA@nokia.com> <4CC1580E.90405@isode.com> <4CC17F36.3070107@ogud.com>
In-Reply-To: <4CC17F36.3070107@ogud.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: port-srv-reg@ietf.org
Subject: Re: [port-srv-reg] Fwd: draft-ietf-tsvwg-iana-ports-07
X-BeenThere: port-srv-reg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of updates to service name and transport protocol port registry <port-srv-reg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/port-srv-reg>, <mailto:port-srv-reg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/port-srv-reg>
List-Post: <mailto:port-srv-reg@ietf.org>
List-Help: <mailto:port-srv-reg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/port-srv-reg>, <mailto:port-srv-reg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 12:12:34 -0000

Olafur Gudmundsson wrote:

> On 22/10/2010 5:23 AM, Alexey Melnikov wrote:
>
>> Lars Eggert wrote:
>>
>>> FYI, from Alfred:
>>>
>>> Begin forwarded message:
>>>
>>>> There are numerous significant and good updates in -07, but also
>>>> a lot of details that still need more work.
>>>> I'm in the process to collect comments and investigate details,
>>>> but mostly busy with own doc's also to be updated before the cutoff.
>>>> So sorry, will need several more days.
>>>>
>>>> BTW: draft-gudmundsson-dnsext-srv-clarify is being updated to
>>>> accommodate the changes to tsvwg-iana-ports-07, and it will be
>>>> out by the cutoff. Please recall that in Hiroshima it had been
>>>> decided that *our* draft performs the updates to RFC 2872 and
>>>> refers normatively to tsvwg-iana-ports for the registry, whereas
>>>> tsvwg-iana-ports will refer to it normatively for the SRV updates
>>>> / clarifications in turn, and both drafts shall be submitted for
>>>> synchronized publication.
>>>> This agreement has been confirmed to us after IETF 76 once more.
>>>> There are changes in -07 that reflect this in part, but in particular
>>>> the front matter and Abstract still say tsvwg-iana-ports Updates 2872.
>>>
>>> My memory is a bit hazy - did we really agree to this?
>>
>> No. I've explained to Alfred the scope of Updates: RFC 2872 in your
>> draft. Maybe I should do that again.
>>
>> So don't do this change.
>
> Lars, yes this was the agreement.
>
> Rather than get into an argument as who does what, lets first
> compile a list of changes to 2782 from each document to weed out any 
> redundancies and then figure out where they fit.

Olafur,
draft-ietf-tsvwg-iana-ports is updating RFC 2782, because it is 
clarifying which IANA registry is to be used for service names.

Your document will most likely be updating both RFC 2782 and 
draft-ietf-tsvwg-iana-ports.