Re: [Dime] Fwd: New Version Notification - draft-ietf-dime-rfc4005bis-10.txt
Benoit Claise <bclaise@cisco.com> Mon, 03 September 2012 16:27 UTC
Return-Path: <bclaise@cisco.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 0DC6F21F86B7 for <dime@ietfa.amsl.com>; Mon, 3 Sep 2012 09:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.367
X-Spam-Level:
X-Spam-Status: No, score=-10.367 tagged_above=-999 required=5 tests=[AWL=0.231, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qin2T9i-24kv for <dime@ietfa.amsl.com>; Mon, 3 Sep 2012 09:27:11 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id BE98B21F86B6 for <dime@ietf.org>; Mon, 3 Sep 2012 09:27:10 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q83GR81G012322; Mon, 3 Sep 2012 18:27:09 +0200 (CEST)
Received: from [10.60.67.90] (ams-bclaise-8919.cisco.com [10.60.67.90]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q83GR8W7006634; Mon, 3 Sep 2012 18:27:08 +0200 (CEST)
Message-ID: <5044DA5B.10804@cisco.com>
Date: Mon, 03 Sep 2012 18:27:07 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120824 Thunderbird/15.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="------------070502000905080505050304"
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: Mon, 03 Sep 2012 16:27:12 -0000
Thanks Glen, I'll progress the draft. Regards, Benoit. > 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