Moby Dick Consolidated System Integration Plan
Share Embed Flag
Download ePaper

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan Moby Dick Consolidated System Integration Plan

kt.agh.edu.pl
from kt.agh.edu.pl More from this publisher
27.03.2014 Views

D0103v1.doc Version 1 6.7.2003 4.5.2.9 AAA message flow This section describes and specifies the message flows. The flows are divided in to request flow and reply flows. The request flow originate from MN and trans the AAA entities towards the AAA server. Whereas the reply flow is the response to the request flow and goes towards the MN. MN MNARq Attendant AAA.f AAA.h ARR.f ARR Request flow MNARp ARA.f ARA Reply flow Figure 84: AAA message flows Note, upon the reception of the ARA, the AAAC.f dumps the NVUP (part of user’s profile) to the QoSB.f. For more details see section: QoS Interface. 4.5.2.9.1 MN to Attendant When the MN is switched on or after the expiration of the authorization lifetime, the MN communicates with the attendant to request an access. As Diameter is not used for communication between an MN and Attendant, the diameter AAA request from the MN must be sent using UDP to the Attendant. Message: MNARq (Mobile Node AAA Request) UDP packet containing an AAA message having the following structure: Parameters: Challenge User-Name MIPv6-Mobile-Node-Address MIPv6-Home -Agent-Address MIP-Binding-Update MN-DH-PV MN-MAC In the following sections the content of the AAA message is listed. Challenge The attendant broadcasts the challenge. The format of the Challenge has the following structure. AVP code: 0xfff00400 Type: Unsigned32 Length: 12 (16 if the 'V' bit is enabled) Value: The challenge MN has got from the Attendant User-Name D0103v1.doc 114 / 168

D0103v1.doc Version 1 6.7.2003 This user name should not be seen as the username in a Unix system. This user name is inferred from the definition as defined in RFC2486. Note: It is to be kept in mind that mobile-IP DOES NOT have anything to do with user names AVP code: 1 Type: UTF8String Length: Variable Contains: NAI /* As defined in RFC2486 / The Network Access Identifier */ MIPv6 -Mobile-Node-Address This address has been specified as it is defined in RFC2486 Diameter Mobile IPv6 Application AVP code: 0xfff00001 /* TBD in the draft */ Type: IPAddress Length: 24 (28 with bit V enabled) /* 16 (IPv6 Addr) + 8 (12) (AVP Header) */ Contains: Mobile's Node Home Address MIPv6 -Home-Agent-Address This is optional since a Home Agent can be assigned automatically. This also defined in RFC 2486 Diameter Mobile IPv6 Application AVP code: 0xfff00002 /* TBD in the draft */ Type: IPAddress Length: 24 (28 with bit V enabled) /* 16 (IPv6 Addr) + 8 (12) (AVP Header) */ Contains: Mobile's Node Home Agent AddressA MIP-Binding-Update The Home Registration as defined in RFC2486. This is optional because it is used only in the scenario in which mobile IP and AAA signalling are combined AVP code: 0xfff00003 /* TBD in the draft */ Type: OctetString Length: Variable Contains: Mobile's Node Home Registration message MN-DH-PV Defined by Moby Dick. AVP containing the public value of the MN's Diffie -Hellman key AVP code: 0xfff00500 Type: OctetString Length: 128 ( 132 when V is set ) Contains: public value of the MN's Diffie-Hellman key MN-MAC Defined by Moby Dick AVP code: 0xfff00004 Type: OctetString Length: 16 ( 20 when V is set ) Contains: HMAC-MD5 over the following AVPs: {Challenge }, { User-Name }, { MIPv6-Mobile-Node-Address } { MIPv6-Home-Agent-Address }, { MIP-Binding-Update } the HMAC-MD5 is computed using SK[MN-AAAC.h] 4.5.2.9.2 Attendant to AAAC.f Once the Attendant has received the UDP packets containing the AAA messages, it will send all the upstream messages using Diameter (i.e. over TCP / SCTP). D0103v1.doc 115 / 168

D0103v1.doc Version 1 6.7.2003<br />

This user name should not be seen as the username in a Unix system. This user name is inferred from the<br />

definition as defined in RFC2486.<br />

Note: It is to be kept in mind that mobile-IP DOES NOT have anything to do with user names<br />

AVP code: 1<br />

Type: UTF8String<br />

Length: Variable<br />

Contains: NAI /* As defined in RFC2486 / The Network Access Identifier */<br />

MIPv6 -Mobile-Node-Address<br />

This address has been specified as it is defined in RFC2486 Diameter Mobile IPv6 Application<br />

AVP code: 0xfff00001 /* TBD in the draft */<br />

Type: IPAddress<br />

Length: 24 (28 with bit V enabled) /* 16 (IPv6 Addr) + 8 (12) (AVP Header) */<br />

Contains: Mobile's Node Home Address<br />

MIPv6 -Home-Agent-Address<br />

This is optional since a Home Agent can be assigned automatically. This also defined in RFC 2486<br />

Diameter Mobile IPv6 Application<br />

AVP code: 0xfff00002 /* TBD in the draft */<br />

Type: IPAddress<br />

Length: 24 (28 with bit V enabled) /* 16 (IPv6 Addr) + 8 (12) (AVP Header) */<br />

Contains: Mobile's Node Home Agent AddressA<br />

MIP-Binding-Update<br />

The Home Registration as defined in RFC2486. This is optional because it is used only in the scenario in<br />

which mobile IP and AAA signalling are combined<br />

AVP code: 0xfff00003 /* TBD in the draft */<br />

Type: OctetString<br />

Length: Variable<br />

Contains: Mobile's Node Home Registration message<br />

MN-DH-PV<br />

Defined by <strong>Moby</strong> <strong>Dick</strong>. AVP containing the public value of the MN's Diffie -Hellman key<br />

AVP code: 0xfff00500<br />

Type: OctetString<br />

Length: 128 ( 132 when V is set )<br />

Contains: public value of the MN's Diffie-Hellman key<br />

MN-MAC<br />

Defined by <strong>Moby</strong> <strong>Dick</strong><br />

AVP code: 0xfff00004<br />

Type: OctetString<br />

Length: 16 ( 20 when V is set )<br />

Contains: HMAC-MD5 over the following AVPs:<br />

{Challenge }, { User-Name }, { MIPv6-Mobile-Node-Address }<br />

{ MIPv6-Home-Agent-Address }, { MIP-Binding-Update }<br />

the HMAC-MD5 is computed using SK[MN-AAAC.h]<br />

4.5.2.9.2 Attendant to AAAC.f<br />

Once the Attendant has received the UDP packets containing the AAA messages, it will send all the<br />

upstream messages using Diameter (i.e. over TCP / SCTP).<br />

D0103v1.doc 115 / 168

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!