Authentication, Authorization, and Accounting (AAA) Goals for Mobile IPv6
RFC 5637

Note: This ballot was opened for revision 01 and is now closed.

Lars Eggert No Objection

(Jari Arkko; former steering group member) Yes

Yes ()
No email
send info

(David Ward; former steering group member) No Objection

No Objection ()
No email
send info

(Lisa Dusseault; former steering group member) No Objection

No Objection ()
No email
send info

(Magnus Westerlund; former steering group member) No Objection

No Objection ()
No email
send info

(Mark Townsley; former steering group member) (was Yes) No Objection

No Objection ()
No email
send info

(Ron Bonica; former steering group member) No Objection

No Objection ()
No email
send info

(Ross Callon; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Tim Polk; former steering group member) (was Discuss) No Objection

No Objection (2008-07-17)
No email
send info
In section 4.2, Integrated Scenario, the acronym AAAH is introduced without any explanation.
It does not appear in RFCs 3775, 4640, or 5026.  It is used but not defined in
mip6-bootstrapping-integrated-dhc.  I finally found it in RFC 4285.  That was painful, and
could have been avoided by either noting that some terms are extracted from [5] in section
2, Terminology, or expanding it on first use.

Nits:

Section 4.1

s/vailidity/validity/

4.2

s/The Home Agent can the assigned/The Home Agent can be assigned/