november 2006ietf67 - ecrit1 a dynamic host configuration protocol (dhcp) based location-to-service...

4
November 2006 IETF67 - ECRIT 1 A Dynamic Host Configuration Protocol (DHCP) based Location-to-Service Translation Protocol (LoST) Discovery Procedure draft-polk-ecrit-dhc-lost-discovery-01 Henning Schulzrinne James Polk Hannes Tschofenig

Upload: hector-hoover

Post on 24-Dec-2015

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: November 2006IETF67 - ECRIT1 A Dynamic Host Configuration Protocol (DHCP) based Location-to-Service Translation Protocol (LoST) Discovery Procedure draft-polk-ecrit-dhc-lost-discovery-01

November 2006 IETF67 - ECRIT 1

A Dynamic Host Configuration Protocol (DHCP) based Location-to-Service

Translation Protocol (LoST) Discovery Procedure

draft-polk-ecrit-dhc-lost-discovery-01

Henning Schulzrinne

James Polk

Hannes Tschofenig

Page 2: November 2006IETF67 - ECRIT1 A Dynamic Host Configuration Protocol (DHCP) based Location-to-Service Translation Protocol (LoST) Discovery Procedure draft-polk-ecrit-dhc-lost-discovery-01

November 2006 IETF67 - ECRIT 2

Overview

• Contains single domain name– encoded as ROTFC 1035 label sequence

• [length] label [length] label [0]• after IDN translation

TBD len RFC 1035 label sequence

OPTION_LOST option-length

7 example 3 com 0

Page 3: November 2006IETF67 - ECRIT1 A Dynamic Host Configuration Protocol (DHCP) based Location-to-Service Translation Protocol (LoST) Discovery Procedure draft-polk-ecrit-dhc-lost-discovery-01

November 2006 IETF67 - ECRIT 3

Resolved: domain name representation

• Domain name representation– RFC 1035 (as in RFC 3264)

• IDN done by application

– LoST URL or IRI• Store UTF-8• IDN done by resolver library

– IDN itself

• Got DHC WG chair guidance (RFC 4702)

Page 4: November 2006IETF67 - ECRIT1 A Dynamic Host Configuration Protocol (DHCP) based Location-to-Service Translation Protocol (LoST) Discovery Procedure draft-polk-ecrit-dhc-lost-discovery-01

November 2006 IETF67 - ECRIT 4

Major change: server count

• Exactly one LoST server– can’t use multiple options (concatenated)

• Multiple servers can be encoded in NAPTR entry