html5-img
1 / 12

DHCP Option for Access Network Information draft-lijun-dhc-clf-nass-option-01

DHCP Option for Access Network Information draft-lijun-dhc-clf-nass-option-01. Jun Li leejun@huawei.com. The Bigger Picture. RFC3455 defines some Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) .

mircea
Download Presentation

DHCP Option for Access Network Information draft-lijun-dhc-clf-nass-option-01

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DHCP Option for Access Network Informationdraft-lijun-dhc-clf-nass-option-01 Jun Li leejun@huawei.com

  2. The Bigger Picture RFC3455 definessome Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP). P-Access-Network-Info Header is one of these headers. The SIP terminal can use it to carry the access network information. So, we need a DHCP option to provide the access network information. Through this Option, the SIP terminal will know the access network information, and will send the information to Service Control Subsystem via P-Access-Network-Info Header.

  3. How this all fits together CPE registered with access network service control subsystem Service Control Subsystem CPE provides P-Access-Network-Info to Service control subsystem CLF CLF NASS NASS NACF(DHCP Server) NACF(DHCP Server) Access network1 Access network2 CPE gets access network identifier via DHCP CPE CPE

  4. From ETSI TISPAN WG2 The service network will cooperate with multi access network in the TISPSN NGN architect. And the service network entity needs to query some information (for example, the access location information) of the user from the access network entity. But as there are multi access network exist, the service network can’t identify which access network attached of this user because the service entity just get the IP address of the user. And the IP address is not enough to locate the access network, especially there are private IP address, mobile IP or nomadize network scenario exists. Now in the TISPAN network, there is some method for user to bring the access network info to service network entity. But the user can’t get any information about the attached access network. So the TISPAN WG2 needs the IETF to give a solution to resolve this issue above.

  5. Changes since IETF 63 • Added terminology section on TISPAN • Verified TISPAN R1 does not need IPv6 • Reworked option to be more generic • “Access Network Information” • Made encoding a sub-option field (easier for implementers)

  6. DHCP Option for Access Network Information The format of the access network information option is: Code Len Access network Information Field +------+------+------+------+------+------+--...-+------+ | TBD | N | i1 | i2 | i3 | i4 | | iN | +------+------+------+------+------+------+--...-+------+ N = number of octets of Access Network Information

  7. DHCP Option for Access Network Information The Access Network Information field consists of a sequence of SubOpt/ Length/ Value tuples for each sub-option, encoded in the following manner: Access Network ID (ANID): SubOpt Len Sub-option Value +------+------+------+------+------+------+--...-+------+ | 1 | N | i1 | i2 | i3 | i4 | | iN | +------+------+------+------+------+------+--...-+------+ Connectivity Session Location and Repository Function (CLF): SubOpt Len Sub-option Value +------+------+------+------+------+------+--...-+------+ | 2 | N | i1 | i2 | i3 | i4 | | iN | +------+------+------+------+------+------+--...-+------+

  8. Next Steps • Who has read the draft? • Is there still work to do on the draft? • Interest in working on the draft? • Do we still need to break out address encoding discussion to a separate document?

  9. THANK YOU !

  10. Background TISPAN NGN Architecture

  11. Background Network Attachment Subsystem (NASS) • The Network Attachment Subsystem provides the following functionalities: • Dynamic provision of IP address and other user equipment configuration parameters (e.g. using DHCP). • User authentication, prior or during the IP address allocation procedure. • Authorisation of network access, based on user profile. • Access network configuration, based on user profile. • Location management. • ------ ETSI TISPAN WI20021

  12. Background TISPAN calls for a new DHCP option: The NACF should be able to provide to the CPE a access network identifier. This information uniquely identifies the access network to which the CPE is attached. With this information applications should be able to locate the CLF. Note: The transport of the access identifier depends on extension in existing protocols (e.g. new DHCP option ) ----- ETSI TISPAN WI02021

More Related