Subject: [i2rs] Questions & suggestions to draft-ietf-i2rs-usecase-reqs-summary-00

From: Linda Dunbar <[email-masked]>
Date: Wed, 25 Feb 2015 19:15:39 +0000

Mach and Sue,

I have some questions and suggestions  for the Section 7:  Req from SFC Use Cases:

-          SFC-US-REQ01:

o   Is the  "service node" here mean "Service Function" Node? Why need the " host system" address? Is "host system address " the Server address When multiple service functions are instantiated on the server? Then the "Server" address is not referenced by Forwarding node. Why need here?

o   It makes more sense to have  "Service Node Address & Service Function Index" tuple to cover the case of one service node having multiple service functions instantiated.

-           SFC-USE-REQ02:

o   SF type should be "Vendor & SF name". FW by different vendors have different functionalities. Same goes IP Firewall, LB, etc.

-          SFC-USE-REQ03:

o   What is the "virtual contexts" for? Is the "Virtual Context" here mean the same as NVo3's "virtual context", i.e. the "Virtual Network Identifier"?

I think Routers have to expose which fields that routers are capable of steering. For example,

-          Steering packets based on L2 Layer: MPLS label, MAC destination, MAC source, VID, EtherType

-          Steering packets based on any field of GRE header, VxLAN header, ..

-          Steering packets based on L3 Layer: IP destination, IP Source, protocol code, ...

-          Steering packets based on L4 fields: TCP port, UDP port

-          Steering packets based on ingress port,

-          Steering packets based on any bits in the packet

-          Steering packets based on packet size,

-          Steering packets based on time of the day,

Linda