Re: [Dime] Fwd: New Version Notification - draft-ietf-dime-rfc4005bis-10.txt
Glen Zorn <glenzorn@gmail.com> Tue, 14 August 2012 12:17 UTC
Return-Path: <glenzorn@gmail.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D7121F8692 for <dime@ietfa.amsl.com>; Tue, 14 Aug 2012 05:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.217
X-Spam-Level:
X-Spam-Status: No, score=-3.217 tagged_above=-999 required=5 tests=[AWL=0.381, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ePJyWTw08Lk4 for <dime@ietfa.amsl.com>; Tue, 14 Aug 2012 05:17:37 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 59CB621F85D0 for <dime@ietf.org>; Tue, 14 Aug 2012 05:17:37 -0700 (PDT)
Received: by yenm5 with SMTP id m5so403565yen.31 for <dime@ietf.org>; Tue, 14 Aug 2012 05:17:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=hfBpLzepNpXAnJrFm5IOW60NaogG/uar1VByK9i2v/8=; b=XPncJrsd2w5QA4BAV99AwbVQi7nsjijwSDe2r5IdCsXejbHnuic2EbZBhf9JqXU1GJ pnOfY4lbW7fuHDCcuFAbUdwWl0DCjYVNRKLS8dNehlMY8eNKdcUDY9Yr17ObmT9wNfZp mizvkXQZug3ll3u1EtbNbGgdq84TxHCjA2EKEuKGfQIQXrybdsOz3b8H7na3TN2d8VAF HavmT8iVoB+3yKfMVafsj0hkzpQV7tC0Dquf8UxY8Bb9pqnr+jrqOc7ZusPm5CNOS7Yw 0KYkY8yg89wnmYXsUiQhR+dNOdV2DrsCO3cv1QYab3wzyte2RMrCh5YHbqwNHDzblXKY J3Qw==
Received: by 10.50.220.194 with SMTP id py2mr11445669igc.15.1344946656444; Tue, 14 Aug 2012 05:17:36 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-122-129-252.revip2.asianet.co.th. [124.122.129.252]) by mx.google.com with ESMTPS id ut5sm21005269igc.13.2012.08.14.05.17.33 (version=SSLv3 cipher=OTHER); Tue, 14 Aug 2012 05:17:35 -0700 (PDT)
Message-ID: <502A41DB.1020609@gmail.com>
Date: Tue, 14 Aug 2012 19:17:31 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120721 Thunderbird/14.0
MIME-Version: 1.0
To: Glen Zorn <glenzorn@gmail.com>
References: <20120715054226.4612.98302.idtracker@ietfa.amsl.com> <500F08AF.4010102@cisco.com> <1343202545.7688.181.camel@gwz-laptop>
In-Reply-To: <1343202545.7688.181.camel@gwz-laptop>
Content-Type: multipart/alternative; boundary="------------050008010005020604050106"
Cc: dime mailing list <dime@ietf.org>
Subject: Re: [Dime] Fwd: New Version Notification - draft-ietf-dime-rfc4005bis-10.txt
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 14 Aug 2012 12:17:38 -0000
On 07/25/2012 02:49 PM, Glen Zorn wrote: Hi. Has this gone to IETF LC already? I didn't see the announcement... > On Tue, 2012-07-24 at 13:42 -0700, Benoit Claise wrote: >> Hi Glen, >> >> Thanks for this new version. >> Two points that need to be addressed. >> >> >> 1. It seems that you have forgotten what we agreed upon on the >> mailing list. >> >> How about this? >> >> OLD: >> 3. Diameter NAS Application Messages >> >> This section defines the Diameter message Command-Code >> [I-D.ietf-dime-rfc3588bis] values that MUST be supported by all >> Diameter implementations conforming to this specification. The >> Command Codes are as follows: >> >> +-----------------------------------+---------+------+--------------+ >> | Command Name | Abbrev. | Code | >> Reference | >> +-----------------------------------+---------+------+--------------+ >> | AA-Request | AAR | 265 | Section >> 3.1 | >> | AA-Answer | AAA | 265 | Section >> 3.2 | >> | Re-Auth-Request | RAR | 258 | Section >> 3.3 | >> | Re-Auth-Answer | RAA | 258 | Section >> 3.4 | >> | Session-Termination-Request | STR | 275 | Section >> 3.5 | >> | Session-Termination-Answer | STA | 275 | Section >> 3.6 | >> | Abort-Session-Request | ASR | 274 | Section >> 3.7 | >> | Abort-Session-Answer | ASA | 274 | Section >> 3.8 | >> | Accounting-Request | ACR | 271 | Section >> 3.9 | >> | Accounting-Answer | ACA | 271 | Section >> 3.10 | >> +-----------------------------------+---------+------+--------------+ >> >> NEW: >> 3. Diameter NAS Application Messages >> >> This section defines the Diameter message Command-Code >> [I-D.ietf-dime-rfc3588bis] values that MUST be supported by all >> Diameter implementations conforming to this specification. The >> Command Codes are as follows: >> >> +-----------------------------------+---------+------+--------------+ >> | Command Name | Abbrev. | Code | >> Reference | >> +-----------------------------------+---------+------+--------------+ >> | AA-Request | AAR | 265 | Section >> 3.1 | >> | AA-Answer | AAA | 265 | Section >> 3.2 | >> | Re-Auth-Request | RAR | 258 | Section >> 3.3 | >> | Re-Auth-Answer | RAA | 258 | Section >> 3.4 | >> | Session-Termination-Request | STR | 275 | Section >> 3.5 | >> | Session-Termination-Answer | STA | 275 | Section >> 3.6 | >> | Abort-Session-Request | ASR | 274 | Section >> 3.7 | >> | Abort-Session-Answer | ASA | 274 | Section >> 3.8 | >> | Accounting-Request | ACR | 271 | Section >> 3.9 | >> | Accounting-Answer | ACA | 271 | Section >> 3.10 | >> +-----------------------------------+---------+------+--------------+ >> >> Note that the message formats in the following sub-sections use >> the standard Diameter Command Code Format >> ([I-D.ietf-dime-rfc3588bis], Section 3.2). >> >> >> >> 2. To be complete, and to let the DIME WG know, let me include what >> we have exchanged in a private email regarding the IANA pointer for >> the application id 1. >> >> You asked for a statement and some consistency from the IESG. >> - statement: The reference should be where the item in question is >> documented, not what registered it. >> - consistency: right, we need to make this clear and not change it. >> Michelle Coton and Barry Leiba are working on an update to BCP 26 >> that will, in part, do just that, and you are welcome to comment on >> it when it's posted (during or shortly after IETF 84). >> >> I propose that you add an "IANA note" in the IANA security section of >> draft-ietf-dime-rfc4005bis-09.txt expressing something such as: as >> discussed with the IESG, application id 1 should point to <RFC4005bis.> >> >> >> >> Please include those two points in the next revision of the draft, >> and I'll progress the draft to IETF LC. > > I'll submit it Monday evening. > > ...
- [Dime] Fwd: New Version Notification - draft-ietf… Benoit Claise
- Re: [Dime] Fwd: New Version Notification - draft-… Glen Zorn
- Re: [Dime] Fwd: New Version Notification - draft-… Glen Zorn
- Re: [Dime] Fwd: New Version Notification - draft-… Benoit Claise