Re: [Int-area] Combined draft on DHCP authentication

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Int-area] Combined draft on DHCP authentication

To: "Iljitsch van Beijnum" <iljitsch at muada.com>, <int-area at ietf.org>
Subject: Re: [Int-area] Combined draft on DHCP authentication
From: <Bernard_Aboba at hotmail.com>
Date: Mon, 19 Nov 2007 05:49:25 -0800
Cc:
Importance: Normal
In-reply-to: <474103CD.3090305@cisco.com> <767FE297-B52A-4812-B6D5-61B09F2D4037@muada.com>
List-archive: <http://www1.ietf.org/pipermail/int-area>
List-help: <mailto:int-area-request@lists.ietf.org?subject=help>
List-id: IETF Internet Area Mailing List <int-area.lists.ietf.org>
List-post: <mailto:int-area@lists.ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@lists.ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@lists.ietf.org?subject=unsubscribe>
References: <474103CD.3090305@cisco.com> <767FE297-B52A-4812-B6D5-61B09F2D4037@muada.com>

Doesn't seem to address IPv6. This makes it useless in my book.

I'm not clear how the specified mechanism would work with address autoconfiguration. Would EAP be encapsulated within an RS/RA exchange?


_______________________________________________
Int-area mailing list
Int-area at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/int-area

Follow-Ups:
- Re: [Int-area] Combined draft on DHCP authentication
  - From: Richard Pruss

References:
- [Int-area] Combined draft on DHCP authentication
  - From: Richard Pruss
- Re: [Int-area] Combined draft on DHCP authentication
  - From: Iljitsch van Beijnum

Prev by Date: Re: [Int-area] Combined draft on DHCP authentication
Next by Date: Re: [Int-area] Combined draft on DHCP authentication
Previous by thread: Re: [Int-area] Combined draft on DHCP authentication
Next by thread: Re: [Int-area] Combined draft on DHCP authentication
Index(es):
- Date
- Thread

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.