1. draft-cordeiro-nsis-hypath-02 Luís Cordeiro cordeiro@dei.uc.pt

2. Luís Cordeiro - cordeiro@dei.uc.pt2 09/11/2006 Summary Changes HyPath as a MRM Conclusions

3. Luís Cordeiro - cordeiro@dei.uc.pt3 09/11/2006 Draft changes Processing in the border router was updated Message Payload changed:  Added the IP version flag  Added the original direction flag  Removed length field Multiple domain HyPath example added

4. Luís Cordeiro - cordeiro@dei.uc.pt4 09/11/2006 How it works now HyPath is a middle layer between GIST and the NSLPs

5. Luís Cordeiro - cordeiro@dei.uc.pt5 09/11/2006 NSIS domains

6. Luís Cordeiro - cordeiro@dei.uc.pt6 09/11/2006 Non NSIS domains

7. Luís Cordeiro - cordeiro@dei.uc.pt7 09/11/2006 Required information 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type |I|B|D| Reserved| nslpID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ // Source Address // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ // Destination Address // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ // Border Router Address // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type: type of HyPath message. 1 - Standard message: a message that follows the data path and it is intercepted in the border routers 2 - Border router message: a message that it is sent from the border router to the RM 3 - Resource Manager message: a message that is sent either to the border router of the actual domain or to the RM of the next domain, depending on the type of the next domain (NSIS or non-NSIS) Flag I: IP version [ 0 = IPv4 | 1 = IPv6 ] Flag B: means that the border router address field is present Flag D: message direction flag NSLPID: Original NSLP ID Source Address: data source address Destination Address: data destination address Border Router Address: border router address to where the resource manager MUST send the next message

8. Luís Cordeiro - cordeiro@dei.uc.pt8 09/11/2006 The new approach GIST allows several types of Message Routing Method (MRM)  Only one is specified until now, the Path- Coupled MRM HyPath should be a new MRM  HyPath MRM

9. Luís Cordeiro - cordeiro@dei.uc.pt9 09/11/2006 How to put it working HyPath MRM should  Include all Path-Coupled information Because most of this information is required for the “normal” routing  Extend the Path-Coupled information New parameters are required Can we make HyPath MRM as an extension of the Path-Coupled MRM?  Is that enough for the protocol to work?  Does the current GIST handle these few changes?

10. Luís Cordeiro - cordeiro@dei.uc.pt10 09/11/2006 HyPath MRM differences from the Path-Coupled MRM When receiving messages:  In RMs: Save the state with the BR information or Save the state with the previous RM information (for non NSIS domains)  In BRs: No NSLP, so forward message (go to sending…) Before sending messages:  In RMs: Get next domain info: NSIS or non NSIS domain? First domain:  NSIS domain: get BR IP address and send message to that BR  Non NSIS domain: get RM IP address and send message to that RM Other domain:  NSIS domain: get state and BR IP address (if not, treat as a first domain) and send message to that BR  Non NSIS domain: same as First domain  In BRs: Message type: 1. If previous BR is from the same domain forward message (can update the BR IP address) 2. Should never happen 3. Use MRM source/destination/direction original information to send message through the data path Processing: no difference?

11. Luís Cordeiro - cordeiro@dei.uc.pt11 09/11/2006 Conclusion HyPath MRM should be PC MRM with more info Changes in GIST should be minor:  When receiving a message if it’s a HyPath MRM do some extra work  When sending a message if it’s a HyPath MRM do some extra work  Only a new state table is needed (in BR’s it’s not needed)

12. Luís Cordeiro - cordeiro@dei.uc.pt12 09/11/2006 What’s your opinion? About the specification? About the implementation?