[dhcwg] Fwd: New Version Notification for draft-ietf-dhc-relay-server-security-04.txt
"Bernie Volz (volz)" <volz@cisco.com> Wed, 29 March 2017 17:25 UTC
Return-Path: <volz@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 D2119129458 for <dhcwg@ietfa.amsl.com>; Wed, 29 Mar 2017 10:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 DOflWqZDjhU7 for <dhcwg@ietfa.amsl.com>; Wed, 29 Mar 2017 10:25:09 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 010D712944F for <dhcwg@ietf.org>; Wed, 29 Mar 2017 10:25:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6910; q=dns/txt; s=iport; t=1490808308; x=1492017908; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=kD4oRGUw+XgyHOZctU9IIuV203xTs6ZthLzka+P6igE=; b=GD835dcbrIrjrPonIN9CmB1unrIZETp62ErqxQ8UGTMxdzllRsvp64pU CifyrkS/28mK+oVowk9LKsbfAhppjYzxjiYNwk5GYOtO6MpRTymhbss18 Mm5fsrrsGmpt1o+a0jfYDiCKv//ktyQfb0Z0/tIvExL47W3uIPLYhdoue 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AXAQAS7dtY/5tdJa1dGQEBAQEBAQEBAQEBBwEBAQEBg1VhgQuFaIgLkVGQHYUxgg4shByBWgKDQz8YAQIBAQEBAQEBax0LhRUBAwN3EgIBGAEDAQIoBzIUBwIIAgQTigoOsBKKUgEBAQEBAQEBAQEBAQEBAQEBAQEBAR2IU4JqgxeBJzYWgn6CMQWPYYx/AYZ8i1OBfFSEVooNk2kBDxA4gQRZFRg6AYQNgjl1AYk1AQEB
X-IronPort-AV: E=Sophos;i="5.36,242,1486425600"; d="scan'208,217";a="400868918"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Mar 2017 17:25:07 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v2THP72R013264 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dhcwg@ietf.org>; Wed, 29 Mar 2017 17:25:07 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 29 Mar 2017 12:25:07 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Wed, 29 Mar 2017 12:25:06 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-dhc-relay-server-security-04.txt
Thread-Index: AQHSqJ/RFGeys8i9JkG7rqmVyJYmPKGsEZLe
Date: Wed, 29 Mar 2017 17:25:06 +0000
Message-ID: <7F37BF6A-0AA9-4E83-B66A-63EB1603D606@cisco.com>
References: <149080074897.26806.14718163560330127333.idtracker@ietfa.amsl.com>
In-Reply-To: <149080074897.26806.14718163560330127333.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_7F37BF6A0AA94E83B66A63EB1603D606ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/eTlu-njsR4gEuNEUDsr7g4WeZ0c>
Subject: [dhcwg] Fwd: New Version Notification for draft-ietf-dhc-relay-server-security-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 29 Mar 2017 17:25:11 -0000
This addresses review comnents from Francis Dupont's GENART review. https://datatracker.ietf.org/doc/review-ietf-dhc-relay-server-security-03-genart-lc-dupont-2017-03-10/ - Bernie (from iPhone) Begin forwarded message: From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> Date: March 29, 2017 at 10:19:08 AM CDT To: Yogendra Pal <yogpal@cisco.com<mailto:yogpal@cisco.com>>, Bernie Volz <volz@cisco.com<mailto:volz@cisco.com>> Subject: New Version Notification for draft-ietf-dhc-relay-server-security-04.txt A new version of I-D, draft-ietf-dhc-relay-server-security-04.txt has been successfully submitted by Bernie Volz and posted to the IETF repository. Name: draft-ietf-dhc-relay-server-security Revision: 04 Title: Security of Messages Exchanged Between Servers and Relay Agents Document date: 2017-03-29 Group: dhc Pages: 8 URL: https://www.ietf.org/internet-drafts/draft-ietf-dhc-relay-server-security-04.txt Status: https://datatracker.ietf.org/doc/draft-ietf-dhc-relay-server-security/ Htmlized: https://tools.ietf.org/html/draft-ietf-dhc-relay-server-security-04 Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-dhc-relay-server-security-04 Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-relay-server-security-04 Abstract: The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has no guidance for how to secure messages exchanged between servers and relay agents. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) states that IPsec should be used to secure messages exchanged between servers and relay agents, but does not require encryption. And, with recent concerns about pervasive monitoring and other attacks, it is appropriate to require securing relay to relay and relay to server communication for DHCPv6 and relay to server communication for DHCPv4. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>. The IETF Secretariat
- [dhcwg] Fwd: New Version Notification for draft-i… Bernie Volz (volz)