Presentation on theme: "Network Service Header (NSH) draft-quinn-sfc-nsh IETF 90"— Presentation transcript:
1 Network Service Header (NSH) draft-quinn-sfc-nsh IETF 90 P. Quinn, et. alCisco SystemsP. AgarwalR. ManurBroadcomPankaj GargMicrosoftA. ChauhanCitrixU. ElzurIntelB. McConnellRackspaceC. WrightRed Hat Inc.
2 NSH OverviewDescribes a dataplane header used to carry information along a service path.Identifier for service path selectionOpaque mandatory metadata fieldsOptional TLVsCreates “service plane”Transport independent (NSH in VXLAN, NSH in MPLS, NSH in UDP, etc.)Service layer OAM
3 Changes from -02 New co-author Base header is first 4 bytes, includes type fieldEncapsulated protocol type 8 bit valueExplicit dataplane versioningCritical TLV indicator4 byte service path headerAdded optional metadata TLV (in addition to mandatory fixed context header)TLV Class
4 Implementation Update Opensource implementationsOVS dataplane (with VXLAN)OpenDaylight control plane (+ LISP)Several vendor specific implementationsEarly deployments underway
5 Base Header|Ver|O|C|R|R|R|R|R|R| Length | MD Type | Next Protocol |8 bit Next Protocol: support non-ET protocols + reclaim spaceMD type indicates format of header. NSH type = 0x1Critical TLV present
6 Service Path Header Represents the rendering of the chain policy | Service Path ID | Service Index |Represents the rendering of the chain policySimple identifier: does not imply a static, explicit pathResolved locallyCan be changed: branching within a service graphRe-classification (and therefore policy) decisionIndex conveys node within the graph
8 Mandatory Context Headers | Network Platform Context | | Network Shared Context | | Service Platform Context | | Service Shared Context |Based on initial deployments: many use cases satisfiedwith fixed size context headersHardware friendly: easy to parse and skip at high speedOpaque, significance allocated via control plane
9 Optional TLV TLV Class: describes the scope of the type field | TLV Class | Type |R|R|R| Len || Variable Metadata |TLV Class: describes the scope of the type fieldType: type of metadata carried, includes critical indication
10 Next Steps Continue development Continued deployments Opensource and vendorsContinued deploymentsAsk for adoption as a working group document: SFC encapsulation“Generic SFC Encapsulation: This document will describe a single service-level data plane encapsulation format that: - indicates the sequence of service functions that make up the Service Function Chain - specifies the Service Function Path, - communicates context information between nodes that implement service functions and Service Function Chains…”
Your consent to our cookies if you continue to use this website.