search

dhcwg / yang

A workplace for IETF drafts related to DHC WG and YANG
1 stars 1 forks source link

Identifiers used in reservations besides DUID #18

Closed zihaohe123 closed 6 years ago

zihaohe123 commented 6 years ago

Although DUID is a most obvious identifier for a client, in many cases it is useless for assigning static reservations because the server administrator doesn't know the DUID util the client contacts the server for the first time. There are other options which can be considered to make a reservation, e.g. MAC address, Remote-id and Subscriber-id. The model should allow for using those (perhaps also some other identifiers) to make static reservations.

bevolz commented 6 years ago

How about generalizing this to just some client identifier and perhaps an enumerated type (DUID, Remote-ID, Subscriber-ID, mac-address, other)?

Note: You should keep the client-identifier (DUID) though since a server can record the DUID even if it uses an alternative identifier. The server must maintain the DUID since that is part of the 3315 protocol.

From: Zihao He notifications@github.com Reply-To: dhcwg/yang reply@reply.github.com Date: Tuesday, January 30, 2018 at 8:42 AM To: dhcwg/yang yang@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [dhcwg/yang] Identifiers used in reservations besides DUID (#18)

Although DUID is a most obvious identifier for a client, in many cases it is useless for assigning static reservations because the server administrator doesn't know the DUID util the client contacts the server for the first time. There are other options which can be considered to make a reservation, e.g. MAC address, Remote-id and Subscriber-id. The model should allow for using those (perhaps also some other identifiers) to make static reservations.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/dhcwg/yang/issues/18, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABm3YZbnlP3FJ7GfajOo3SdPcgjrdO9Qks5tPxwpgaJpZM4RyWGo.

zihaohe123 commented 6 years ago

Yes. I think we could just add 'mac-address', 'remote-id' and 'subscriber-id' as non-mandatory nodes under reserved-addresses/prefixes. However, I still don't see what an administrator should do if he has no idea of the client's DUID when making reservations since DUID is mandatory here. (Maybe it doesn't need further discussions and is out of the scope of this yang model ?)