@techreport{ao-sfc-transport-00,
    number =    {draft-ao-sfc-transport-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ao-sfc-transport/00/},
    author =    {Ting Ao and Wei Wei and Yan Zheng},
    title =     {{SFC transport considertation}},
    pagetotal = 10,
    year =      2018,
    month =     oct,
    day =       22,
    abstract =  {A Network Service Header(NSH) is imposed encapsulates a packet or a frame for Service Function Chaining. The resulting packet, in turn, is encapsulate according to transport layer. The NSH contains a Service Path Identifier (SPI) and a Service Index (SI). The SPI is, as per its name, an identifier. The SPI alone cannot be used to forward packets along a service path. Rather, the SPI provides a level of indirection between the service path / topology and the network transport encapsulation. For different transport encapsulations, this document provides the format information with transport and NSH, and gives operational constraints that transport technologies, used by NSH need to meet.},
}