Moby Dick Consolidated System Integration Plan

More documents

Recommendations

Info

D0103v1.doc Version 1 6.7.2003 4.7.2.2 Alternate Care-of Address support In order to support the alternate-CoA registration with a binding update, which is required for Paging, the Mobile IPv6 implementation is to be patched with an appropriate alt-CoA patch, which was implemented within the framework of WP3 activities. D0103v1.doc 146 / 168
D0103v1.doc Version 1 6.7.2003 5 Moby Dick Signalling Flow Specification This chapter reports about the specification of signalling and message flows for initial registration, fast intra-domain handover, inter-domain handover and Paging with respect to mobility, QoS and AAA. Thus, this version contains all required information for a reader to understand the way, how the components as described in the previous chapter will interact in the deployed Moby Dick architecture. Since the specification allows several possible implementations, the structure of the following section comprises for all scenarios the functional specification and the detailed implementation specification. 5.1 Assumptions This section lists the assumptions and specifies the interface between WP2 (QoS), WP3 (Mobility) and WP4 (AAA), especially with respect to implementation issues, since there is the need for ‘message combination’ during the Moby Dick key scenarios, which are registration, handover signalling within and between administrative domains, session setup, paging, Auditing and charging. Interaction and Interfaces between all involved components as described in the previous chapter have been defined. 5.1.1 Security Associations Within the current Moby Dick approach, the following security associations are assumed: Static MN - AAAC.h AAAC.h – HA MN – HA oARx – nAR AAAC.f - AAAC.h AR - AAAC.f MN – PA PA - ARx Dynamic MN – ARx MN - PA Table 45: Security Associations In the framework of Moby Dick, we assume a security association of neighbour Access Routers within an administrative domain. This assumption is also part of the fast-handover draft [draft-ietf-mobileip -fastmipv6-03.txt; section 5.2.1]. This means that dynamic attachment of a user to a domain is out of the scope of Moby Dick. It is assumed that each user has a fixed home domain where he is registered and when asking for resources, this so called home domain is asked for enabling this resources vouching for the user towards any visiting domain. 5.1.2 Distinction: Registration, fast intra-domain and inter-domain handover There is the need to distinguish between Registration, fast intra-domain and inter-domain handover, since all the scenarios require different handling / procedures. This section identifies the entity on which the decision algorithm should be located and presents the parameters on which the decision is based. Intra-domain handover requires a fast handover procedure (i.e., communication between new Access Router and old Access Router), while for the registration and for inter-domain handover the involvement of AAAC.h and Home Agent is required. The reason for this distinction is the assumption, that the provider of a domain a MN is about to leave, in the following called old domain, has not necessarily any contractual relationship with the provider of the domain the MN is about to join, in the following called new domain. But both providers, the provider of the old domain and the provider of the new domain have a business relationship with the provider of the home domain of the user currently using the MN. Within the framework of Moby Dick, special focus will be on intra-domain handover, since inter-domain handovers are expected to occur more rarely and will not be seamless, since the involvement of ‘far away’ network entities is required.) In order to keep this decision transparent to the Mobile IP stack, it is suggested to place this decision algorithm ‘below’ Mobile IP (i.e., in the MTNM). The parameters on which the decision is based are: • Binding cache (i.e., no entry: registration; valid entry: handover) • Analysis of the router advertisement prefix, in order to distinguish between intra and interdomain Several theoretical work is ongoing to extend and to enhance this decision finding process by AAA, QoS and possibly higher layer input such ay payment preferences and so on. D0103v1.doc 147 / 168
Page 1 and 2:
IST-2000-25394 Moby Dick D0103 Moby
Page 3 and 4:
D0103v1.doc Version 1 6.7.2003 4.2.
Page 5 and 6:
D0103v1.doc Version 1 6.7.2003 5.1.
Page 7 and 8:
D0103v1.doc Version 1 6.7.2003 Abbr
Page 9 and 10:
D0103v1.doc Version 1 6.7.2003 1 In
Page 11 and 12:
D0103v1.doc Version 1 6.7.2003 3 Mo
Page 13 and 14:
D0103v1.doc Version 1 6.7.2003 Doma
Page 15 and 16:
D0103v1.doc Version 1 6.7.2003 NCP
Page 17 and 18:
D0103v1.doc Version 1 6.7.2003 It w
Page 19 and 20:
D0103v1.doc Version 1 6.7.2003 curr
Page 21 and 22:
D0103v1.doc Version 1 6.7.2003 •
Page 23 and 24:
D0103v1.doc Version 1 6.7.2003 No A
Page 25 and 26:
D0103v1.doc Version 1 6.7.2003 o Fo
Page 27 and 28:
D0103v1.doc Version 1 6.7.2003 NCP
Page 29 and 30:
D0103v1.doc Version 1 6.7.2003 4.1.
Page 31 and 32:
D0103v1.doc Version 1 6.7.2003 4.1.
Page 33 and 34:
D0103v1.doc Version 1 6.7.2003 asso
Page 35 and 36:
D0103v1.doc Version 1 6.7.2003 Mobi
Page 37 and 38:
D0103v1.doc Version 1 6.7.2003 WP4
Page 39 and 40:
D0103v1.doc Version 1 6.7.2003 Para
Page 41 and 42:
D0103v1.doc Version 1 6.7.2003 Ackn
Page 43 and 44:
D0103v1.doc Version 1 6.7.2003 inst
Page 45 and 46:
D0103v1.doc Version 1 6.7.2003 MT P
Page 47 and 48:
D0103v1.doc Version 1 6.7.2003 The
Page 49 and 50:
D0103v1.doc Version 1 6.7.2003 RtSo
Page 51 and 52:
D0103v1.doc Version 1 6.7.2003 auth
Page 53 and 54:
D0103v1.doc Version 1 6.7.2003 In a
Page 55 and 56:
D0103v1.doc Version 1 6.7.2003 AR s
Page 57 and 58:
D0103v1.doc Version 1 6.7.2003 4.2.
Page 59 and 60:
D0103v1.doc Version 1 6.7.2003 Even
Page 61 and 62:
D0103v1.doc Version 1 6.7.2003 4.2.
Page 63 and 64:
D0103v1.doc Version 1 6.7.2003 Filt
Page 65 and 66:
D0103v1.doc Version 1 6.7.2003 4.2.
Page 67 and 68:
D0103v1.doc Version 1 6.7.2003 •
Page 69 and 70:
Page 71 and 72:
D0103v1.doc Version 1 6.7.2003 is t
Page 73 and 74:
D0103v1.doc Version 1 6.7.2003 4.3
Page 75 and 76:
D0103v1.doc Version 1 6.7.2003 4.3.
Page 77 and 78:
D0103v1.doc Version 1 6.7.2003 This
Page 79 and 80:
D0103v1.doc Version 1 6.7.2003 This
Page 81 and 82:
D0103v1.doc Version 1 6.7.2003 4.3.
Page 83 and 84:
D0103v1.doc Version 1 6.7.2003 4.3.
Page 85 and 86:
Page 87 and 88:
D0103v1.doc Version 1 6.7.2003 4.3.
Page 89 and 90:
D0103v1.doc Version 1 6.7.2003 be u
Page 91 and 92:
D0103v1.doc Version 1 6.7.2003 o Ma
Page 93 and 94:
D0103v1.doc Version 1 6.7.2003 Gene
Page 95 and 96: D0103v1.doc Version 1 6.7.2003 Upli
Page 97 and 98: D0103v1.doc Version 1 6.7.2003 Now
Page 99 and 100: D0103v1.doc Version 1 6.7.2003 3. D
Page 101 and 102: D0103v1.doc Version 1 6.7.2003 User
Page 103 and 104: D0103v1.doc Version 1 6.7.2003 Inte
Page 105 and 106: D0103v1.doc Version 1 6.7.2003 User
Page 107 and 108: D0103v1.doc Version 1 6.7.2003 Serv
Page 109 and 110: D0103v1.doc Version 1 6.7.2003 S1 E
Page 111 and 112: D0103v1.doc Version 1 6.7.2003 The
Page 113 and 114: D0103v1.doc Version 1 6.7.2003 Old
Page 115 and 116: D0103v1.doc Version 1 6.7.2003 This
Page 117 and 118: D0103v1.doc Version 1 6.7.2003 Leng
Page 119 and 120: D0103v1.doc Version 1 6.7.2003 4.5.
Page 121 and 122: D0103v1.doc Version 1 6.7.2003 MN M
Page 125 and 126: D0103v1.doc Version 1 6.7.2003 Afte
Page 127 and 128: D0103v1.doc Version 1 6.7.2003 Pack
Page 131 and 132: D0103v1.doc Version 1 6.7.2003 miss
Page 133 and 134: D0103v1.doc Version 1 6.7.2003 Conn
Page 137 and 138: D0103v1.doc Version 1 6.7.2003 Acce
Page 139 and 140: D0103v1.doc Version 1 6.7.2003 Logg
Page 141 and 142: D0103v1.doc Version 1 6.7.2003 repr
Page 143 and 144: D0103v1.doc Version 1 6.7.2003 Type
Page 145: D0103v1.doc Version 1 6.7.2003 o DM
Page 149 and 150: D0103v1.doc Version 1 6.7.2003 MN A
Page 151 and 152: D0103v1.doc Version 1 6.7.2003 3 AA
Page 153 and 154: D0103v1.doc Version 1 6.7.2003 give
Page 155 and 156: D0103v1.doc Version 1 6.7.2003 9 Ha
Page 157 and 158: D0103v1.doc Version 1 6.7.2003 MN 1
Page 161 and 162: D0103v1.doc Version 1 6.7.2003 No.
Page 163 and 164: D0103v1.doc Version 1 6.7.2003 The
Page 165 and 166: D0103v1.doc Version 1 6.7.2003 MN R
Page 167 and 168: D0103v1.doc Version 1 6.7.2003 for
show all

Moby Dick Consolidated System Integration Plan

Create successful ePaper yourself

Delete template?

Save as template?