Protocol Action: 'DHCP options for PANA Authentication Agents' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Mon, 15 January 2007 21:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6ZVF-0007mO-RU; Mon, 15 Jan 2007 16:36:29 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6ZVD-0007jV-LP; Mon, 15 Jan 2007 16:36:27 -0500
Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H6ZVD-0003N4-C0; Mon, 15 Jan 2007 16:36:27 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 4CA162ACAA; Mon, 15 Jan 2007 21:35:57 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1H6ZUj-0005H2-27; Mon, 15 Jan 2007 16:35:57 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1H6ZUj-0005H2-27@stiedprstage1.ietf.org>
Date: Mon, 15 Jan 2007 16:35:57 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: dhc mailing list <dhcwg@ietf.org>, dhc chair <dhc-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'DHCP options for PANA Authentication Agents' to Proposed Standard
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

The IESG has approved the following document:

- 'DHCP options for PANA Authentication Agents '
   <draft-ietf-dhc-paa-option-05.txt> as a Proposed Standard

This document is the product of the Dynamic Host Configuration Working 
Group. 

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-paa-option-05.txt

Technical Summary
 
  The document specifies a DHCPv4 option and a DHCPv6 option that
  allow a PANA client to learn addresses of PANA Authentication
  Agents.

Working Group Summary
 
  There was consensus for adopting this draft at the wg meeting at
  IETF 63.  Consensus was verified on the mailing list, and got
  adopted in September 2005.  After that it has been discussed in
  both dhc and pana WGs and rev 03 went to a joint WGLC in dhc and
  pana WGs in August 2006.  Based on comments received during last
  call rev 04 was produced.
 
Protocol Quality
 
  The protocol specified in this document specifies new DHCPv4 and
  DHCPv6 options and as there are no special requirements on option
  encodings or usage, this should be trivial to implement.

  This specification was reviewed for the IESG by Jari Arkko.

Note to RFC Editor
 
  Please change the definition of " PANA Authentication Agent 
  (PAA)" in Section 3 to the following:

      The protocol entity in the access network whose responsibility is
      to verify the credentials provided by a PANA client (PaC) and
      authorize network access to the access device.  The PAA and the
      EAP authenticator (and optionally the EAP server) are co-located
      in the same node.

  In Section 7, change

     a PANA Client could be led to
     contact a rogue PANA Authentication Agent, possibly one that then
     intercepts call requests or denies service.

  to

     a PANA Client could be led to contact a rogue PANA
     Authentication Agent, possibly one that then intercepts
     authentication requests and/or denies network access
     to the access device.

  Similarly in Section 7, change

     In most of the networks, 

  to

     In most of networks, 

  And finally in Section 8, change

     Norten

  to

     Narten


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce