[Dime] New snapshot of -02 draft

Steve Donovan <srdonovan@usdonovans.com> Wed, 26 March 2014 17:17 UTC

Return-Path: <srdonovan@usdonovans.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 773C51A01AF for <dime@ietfa.amsl.com>; Wed, 26 Mar 2014 10:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.561
X-Spam-Level: **
X-Spam-Status: No, score=2.561 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kEbGE7bEaw0K for <dime@ietfa.amsl.com>; Wed, 26 Mar 2014 10:17:20 -0700 (PDT)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [23.235.209.16]) by ietfa.amsl.com (Postfix) with ESMTP id 159DE1A0182 for <dime@ietf.org>; Wed, 26 Mar 2014 10:17:20 -0700 (PDT)
Received: from [137.254.4.56] (port=40630 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1WSrRv-0004Wn-Mp for dime@ietf.org; Wed, 26 Mar 2014 10:17:17 -0700
Message-ID: <53330BAC.8010301@usdonovans.com>
Date: Wed, 26 Mar 2014 12:17:32 -0500
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "dime@ietf.org" <dime@ietf.org>
Content-Type: multipart/alternative; boundary="------------070602050807070806040601"
X-OutGoing-Spam-Status: No, score=-1.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz131.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - usdonovans.com
X-Get-Message-Sender-Via: biz131.inmotionhosting.com: authenticated_id: srdonovan@usdonovans.com
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/BZLx1Gp3YFWxvZW7VwjlDiU11Qk
Subject: [Dime] New snapshot of -02 draft
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 26 Mar 2014 17:17:21 -0000

All,

I have put a new snapshot of the -02 draft on the github server.

https://github.com/jounikor/draft-docdt-dime-ovli/blob/master/draft-ietf-dime-ovli-02.txt

This shapshot adds updates for issues 36, 44, 46, 54 and 56.  This
brings the total number of issues resolved with updates to the -02 draft
to 17 plus three that were considered duplicates and two that were
closed with no change.

We still have a chance to get the following issues resolved:

#31 - Ulrich proposed wording that I will include in the next snapshot
unless someone objects soon.

#40 - This is suggested wording for a couple of definitions.  I'll take
the liberty to add these definitions and if I get them wrong we can
address it in -03

#43 - Ben suggested wording that I will include in the next snapshot
unless someone objects soon.

#48 - This deals with the m-bit.  I think we have consensus that there
needs to be wording saying that the m-bit should not be set but we don't
have detailed wording suggested.  If someone can come up with that
wording, I'm more than happy to include it in the next snapshot.

#49 - This deals with capability exchange.  We might already have all of
the wording changes resulting from other issues.  For instance, one of
the resolutions was that the scope of a capability announcement is a
single transaction.  I will look to see if I think this is already
resolved and come back with a recommendation.  I encourage others to do
so as well.

The following issues are tied into the ongoing discussion on Realm and RRR:

23, 55, 57 and 58.  I'll make changes if we come to consensus. 

This leaves the following for after -02 is published.

#25 - End point definition
#26, 27, 60, 61 - Agent behavior definition  (depends on #26)
#61 - Clean up of overview

Regards,

Steve