Re: [Pana] AD review of draft-ietf-dhc-paa-option-04.txt

Jari Arkko <jari.arkko@piuha.net> Tue, 31 October 2006 11:21 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gergh-0008BG-VC; Tue, 31 Oct 2006 06:21:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gergh-0008BB-8u for pana@ietf.org; Tue, 31 Oct 2006 06:21:47 -0500
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gergc-000844-TR for pana@ietf.org; Tue, 31 Oct 2006 06:21:47 -0500
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7818789883; Tue, 31 Oct 2006 13:21:39 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 71F9589882; Tue, 31 Oct 2006 13:21:38 +0200 (EET)
Message-ID: <454731C3.1040305@piuha.net>
Date: Tue, 31 Oct 2006 13:21:39 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>, lionel.morand@orange-ft.com
Subject: Re: [Pana] AD review of draft-ietf-dhc-paa-option-04.txt
References: <0MKp2t-1GXmBA2Eos-0000rI@mrelay.perfora.net>
In-Reply-To: <0MKp2t-1GXmBA2Eos-0000rI@mrelay.perfora.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
Errors-To: pana-bounces@ietf.org

I am fine with the approach that the option is
merely for PAA address discovery, not affecting
whether PANA is on or not. But I would like that
to be explicitly stated in the document. It would
also be useful to have a warning that there are
issues if you attempt to do otherwise.

Changes needed to state are likely fairly small.
If you submit the draft it probably appears when
the IETF starts and I can move the draft along
after that.
> "A PaC SHOULD request the PAA DHCPv4 Option in a Parameter Request List
> as described in [RFC2131] and [RFC2132].
> If configured with a (list of) PAA address(es), a DHCPv4 server SHOULD
> send a client with the PAA DHCPv4 option, even if this option is not
> explicitly requested by the client."
This is a start. It defines what the nodes do, but I
would also like to see

1) What the PaC does when it receives the option
2) Explanation that the option is not used for turning PANA on/off,
along with the warning

--Jari


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana