[dhcwg] draft-ietf-dhc-dhcpv6-failover-protocol-04.txt

kkinnear <kkinnear@cisco.com> Mon, 23 January 2017 20:03 UTC

Return-Path: <kkinnear@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 498C3129858 for <dhcwg@ietfa.amsl.com>; Mon, 23 Jan 2017 12:03:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.721
X-Spam-Level:
X-Spam-Status: No, score=-17.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 R6U1_GM62g6F for <dhcwg@ietfa.amsl.com>; Mon, 23 Jan 2017 12:03:18 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EAE8129BA5 for <dhcwg@ietf.org>; Mon, 23 Jan 2017 12:03:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=868; q=dns/txt; s=iport; t=1485201795; x=1486411395; h=from:content-transfer-encoding:subject:date:message-id: cc:to:mime-version; bh=mfNkSf16kkNEwopNV/5WhPr05+N28ZnytDJJMSvtliA=; b=SVqqlu6JXckFILDx2GaLAlCMbcVdn/8xytu6s61SrgDLzYXPUAeNW2jn kzrFcXadSpGbmE9fgZQs3yc5TtfUqfkOZtK8pBb/s1maD16QF2dpVeiI1 pMhe681ixuYz+8gF6GwzXczgyvtAsKDPx+jjr3ilw49UpREoi8GiS/wXF Y=;
X-IronPort-AV: E=Sophos;i="5.33,275,1477958400"; d="scan'208";a="376114003"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Jan 2017 20:03:15 +0000
Received: from dhcp-161-44-67-120.cisco.com (dhcp-161-44-67-120.cisco.com [161.44.67.120]) (authenticated bits=0) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v0NK3CNH032536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Jan 2017 20:03:13 GMT
From: kkinnear <kkinnear@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 23 Jan 2017 15:03:16 -0500
Message-Id: <77327D85-EE3A-4B98-A91E-6FE36ADE063C@cisco.com>
To: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-Authenticated-User: kkinnear@cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/V-LQrSgbfpR_D5vDeAwnw5YER7Y>
Cc: Kim Kinnear <kkinnear@cisco.com>
Subject: [dhcwg] draft-ietf-dhc-dhcpv6-failover-protocol-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2017 20:03:19 -0000

I have posted a new version of the DHCPv6 failover draft:

	draft-ietf-dhc-dhcpv6-failover-protocol-04.txt.

It contains the following relatively minor editorial changes 
from the -03.txt:

1. A sequence diagram was added to Section 4.4.1 to better explain
   the example given of the way that the MCLT can operate.

2. The text explaining the bit orientation of the flags was
   corrected in Sections:

  5.5.2 OPTION_F_CONNECT_FLAGS 
  5.5.6 OPTION_F_DNS_FLAGS
  5.5.18 OPTION_F_SERVER_FLAGS

3. The bits which are MBZ in Section 5.5.18 OPTION_F_SERVER_FLAGS
   were corrected and the ordering of the bit descriptions was brought
   into line with the other options.
  
4. The spelling in Section 12 of Shawn Routhier's name was
   corrected.

There were no changes to the protocol due to these corrections
and additions.

Regards -- Kim