Re: [port-srv-reg] Slides for TSVWG on draft-ietf-tsvwg-iana-ports
Olafur Gudmundsson <ogud@ogud.com> Mon, 22 March 2010 16:59 UTC
Return-Path: <ogud@ogud.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 B5AF23A6B4E for <port-srv-reg@core3.amsl.com>;
Mon, 22 Mar 2010 09:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.503
X-Spam-Level:
X-Spam-Status: No, score=-1.503 tagged_above=-999 required=5 tests=[AWL=-0.034,
BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 Z8vy5hcWgTKT for
<port-srv-reg@core3.amsl.com>; Mon, 22 Mar 2010 09:59:34 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by
core3.amsl.com (Postfix) with ESMTP id A34FF3A6978 for
<port-srv-reg@ietf.org>; Mon, 22 Mar 2010 09:59:34 -0700 (PDT)
Received: from [IPv6:::1] (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com
(8.14.3/8.14.3) with ESMTP id o2MGxpEZ016406 for <port-srv-reg@ietf.org>;
Mon, 22 Mar 2010 12:59:51 -0400 (EDT) (envelope-from ogud@ogud.com)
Message-ID: <4BA7A205.8020909@ogud.com>
Date: Mon, 22 Mar 2010 12:59:49 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB;
rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: port-srv-reg@ietf.org
References: <4BA56C8A.30205@ericsson.com>
<4BA6FAB6.10101@isode.com> <4BA79127.1010907@ericsson.com>
<4BA79C64.1050104@ericsson.com>
In-Reply-To: <4BA79C64.1050104@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 10.20.30.4
Subject: Re: [port-srv-reg] Slides for TSVWG on draft-ietf-tsvwg-iana-ports
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: Mon, 22 Mar 2010 16:59:35 -0000
Magnus, slides look fine, you are missing the action item that I requested that the draft contain the format of the registry so Alfred and I can generate the registry clean-up document that will update this document and move registrations around etc. Olafur On 22/03/2010 12:35 PM, Magnus Westerlund wrote: > Hi, > > Update version of the slides > > Magnus > > Magnus Westerlund skrev 2010-03-22 08:47: >> Hi Alexey, >> >> The slides was a start collecting the issues. I was hoping that someone >> would pick it up and do a pass over them to create something more useful. >> >> Regarding the reference. We clearly have interactions between the >> documents and those needs to be sorted out. One possibility that I >> proposed was that Olafurs document would need to update this one as it >> comes out. But see discussion on TSVWG mailing list. >> >> Cheers >> >> Magnus >> >> Alexey Melnikov skrev 2010-03-21 22:05: >>> Magnus Westerlund wrote: >>>> Hi, >>>> >>>> I looked through the emails I had in my folders and constructed the >>>> attached slides. As TSVWG is on Monday we don't have a lot of time. My >>>> question to all of you are that you help identify the ones that aren't >>>> simple editorial and where we might not have consensus. >>>> >>>> Please rehash these slides in anyway you want. >>> I only have 1 general comment about your slides (which look fine >>> otherwise). It would be nice to know how you suggest to address various >>> issue. Your slides list all issues, but they don't say if all issues >>> will be addressed. >>> >>> I personally think that not all of them should be addressed. For example >>> I am not convinced that the reference to >>> draft-gudmundsson-dnsext-srv-clarify needs to be normative. >>> >>> >> >> > > > > > _______________________________________________ > Port-srv-reg mailing list > Port-srv-reg@ietf.org > https://www.ietf.org/mailman/listinfo/port-srv-reg
- [port-srv-reg] Slides for TSVWG on draft-ietf-tsv… Magnus Westerlund
- Re: [port-srv-reg] Slides for TSVWG on draft-ietf… Alexey Melnikov
- Re: [port-srv-reg] Slides for TSVWG on draft-ietf… Magnus Westerlund
- Re: [port-srv-reg] Slides for TSVWG on draft-ietf… Magnus Westerlund
- Re: [port-srv-reg] Slides for TSVWG on draft-ietf… Alexey Melnikov
- Re: [port-srv-reg] Slides for TSVWG on draft-ietf… Olafur Gudmundsson
- Re: [port-srv-reg] Slides for TSVWG on draft-ietf… Magnus Westerlund
- Re: [port-srv-reg] Slides for TSVWG on draft-ietf… Olafur Gudmundsson
- Re: [port-srv-reg] Slides for TSVWG on draft-ietf… Joe Touch