| Re: Review of EAP MAKE Type Allocation Request | <– Date –> <– Thread –> |
|
From: Jari Arkko (jari.arkko |
|
| Date: Wed, 11 Jan 2006 07:50:45 -0800 (PST) | |
Bernard Aboba wrote
I agree that this is confusing. We can't have the same know, or we'll
never figure out later what is going on. From a quick review of draft-berrendo
and draft-vanderveen, however, it seems that these are different protocols.
If Michaela submitted her draft and request under a different name (say,
EAP Flarion MAKE), would that remove this particular problem?
--Jari
Given that a Type Code has already been allocated to EAP MAKE, a request for an additional Type Code allocation for the same protocol would represent a "block allocation" as described in RFC 3748,
I agree that this is confusing. We can't have the same know, or we'll
never figure out later what is going on. From a quick review of draft-berrendo
and draft-vanderveen, however, it seems that these are different protocols.
If Michaela submitted her draft and request under a different name (say,
EAP Flarion MAKE), would that remove this particular problem?
--Jari
-
Review of EAP MAKE Type Allocation Request Bernard Aboba, January 7 2006
- Re: Review of EAP MAKE Type Allocation Request Jari Arkko, January 11 2006
- Re: Review of EAP MAKE Type Allocation Request Bernard Aboba, January 11 2006
-
RE: Review of EAP MAKE Type Allocation Request Vanderveen, Michaela, January 11 2006
- RE: Review of EAP MAKE Type Allocation Request Bernard Aboba, January 11 2006
Results generated by Tiger Technologies using MHonArc.