Metadata Considerations draft-rijsman-sfc-metadata-considerations-00 Service Function Chaining Working Group IETF 89 - London - March 2014 Authors: Bruno.

Slides:



Advertisements
Similar presentations
Draft-mackie-sfc-using-virtual-networking-02 S. Mackie, B. Rijsman, Juniper Networks M. Napierala, AT&T D. Daino, Telecom Italia D.R. Lopez, Telefonica.
Advertisements

Internetworking II: MPLS, Security, and Traffic Engineering
Network Service Header (NSH) draft-quinn-sfc-nsh IETF 90
Network Based Services in Mobile Networks Context, Typical Use Cases, Problem Area, Requirements IETF 87 Berlin, 29 July 2013 BoF Meeting on Network Service.
Brief Background Service functions are used in almost every network
State of Connecticut Department of Information Technology Single Sign On and The Identity Vault Presented by Edward Wilson.
Options or payload? Costin Raiciu UCL IETF 78, Maastricht.
OpenDaylight: Service Function Chaining.
Report of Interconnectivity Testing of Service Function Chaining by Six Companies NTT Alaxala Networks Cisco Systems Hitachi Alcatel-Lucent Japan et al.
CS320 Web and Internet Programming Handling HTTP Requests Chengyu Sun California State University, Los Angeles.
CS 142 Lecture Notes: HTTPSlide 1 HTTP Request GET /index.html HTTP/1.1 Host: User-Agent: Mozilla/5.0 Accept: text/html, */* Accept-Language:
Web Application Security 101 Steve Carter (special thanks to SPI Dynamics)
Gursharan Singh Tatla Transport Layer 16-May
SP Wi-Fi Services over Residential Architectures (draft-gundavelli-v6ops-community-wifi-svcs) IETF 84 - August, 2012 Authors: Sri Gundavelli(Cisco) Mark.
Abstraction and Control of Transport Networks (ACTN) BoF
Network Hardware for Expanding Network. Expanding Networks When do we need expansion:  Network cable is full of data movements  Printing tasks needs.
Service Function Chaining in Mobile Networks Status draft-haeffner-sfc-use-case-mobility IETF 89 London, 3 March 2014 Service Function Chaining WG Walter.
Authorization architecture sketches draft-selander-core-access-control-02 draft-gerdes-core-dcaf-authorize-02 draft-seitz-ace-design-considerations-00.
Basics of the HTTP Protocol and Apache Web Server Brandon Checketts.
HTTP – HyperText Transfer Protocol
Service Function Chaining Use Cases draft-liu-service-chaining-use-cases IETF 89 London, March 3, 2014 Will Liu, Hongyu Li, Oliver Huang, Huawei Technologies.
Application Layer 2 Figures from Kurose and Ross
IETF SFC: Service Chain Header draft-zhang-sfc-sch-01
Department of Electronic Engineering City University of Hong Kong EE3900 Computer Networks Introduction Slide 1 A Communications Model Source: generates.
CS320 Web and Internet Programming Handling HTTP Requests Chengyu Sun California State University, Los Angeles.
Proxy Lab Recitation I Monday Nov 20, 2006.
1 SAE architecture harmonization R RAN2/3, SA2 Drafting Group.
Vic Liu Liang Xia Zu Qiang Speaker: Vic Liu China Mobile Network as a Service Architecture draft-liu-nvo3-naas-arch-01.
HTTP1 Hypertext Transfer Protocol (HTTP) After this lecture, you should be able to:  Know how Web Browsers and Web Servers communicate via HTTP Protocol.
1 IETF 78: NETEXT Working Group IPSec/IKEv2 Access Link Support in Proxy Mobile IPv6 IPSec/IKEv2-based Access Link Support in Proxy Mobile IPv6 Sri Gundavelli.
William Stallings Data and Computer Communications
HTTP/2 and ATS ATS Fall Summit 2015 Bryan Call. Why HTTP/2? Reduce latency and TCP connection overhead Easier to write well-performing sites (no domain.
CellSDN: Software-Defined Cellular Core networks Xin Jin Princeton University Joint work with Li Erran Li, Laurent Vanbever, and Jennifer Rexford.
Multipath TCP ACM Queue, Volume 12 Issue 2, pp. 1-12, February 2014 Christoph Paasch and Olivier Bonaventure University College London 1.
Multipath TCP Signaling Options or Payload? Costin Raiciu
Overview of Servlets and JSP
PCE 64 th IETF PCE Policy Architecture draft-berger-pce-policy-architecture-00.txt Lou Berger Igor Bryskin Dimitri Papadimitriou.
BBF Liaison on Service Chaining Hongyu Li Co-editor of SD-326 Flexible Service Chaining
LURP Details. LURP Lab Details  1.Given a GET … call a proxy CGI script in the same way you would for a normal CGI request  2.This UDP perl.
MIP6 WG IETF-68 Service Selection for Mobile IPv6 draft-korhonen-mip6-service-01 March, 2007 Jouni Korhonen, Ulf Nilsson, Vijay Devarapalli.
Web Caching. Why Caching? Faster browsing experience for users Cache hit rate Traffic Prioritization Reduce network bandwidth requirements significantly.
Generic Aggregation of Resource Reservation Protocol (RSVP) for IPv4 and IPv6 Reservation over PCN domains Georgios Karagiannis, Anurag Bhargava draft-karagiannis-pcn-tsvwg-rsvp-pcn-01.
ATM Protocol Architecture Mode. ATM architecture uses a logical reference model to describe its functions ATM functions correspond to physical layer and.
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Performance testing and engineering Raja Gourav Kokkiligadda, Performance Architect, Domestic and General.
Applicability of Proxy Mobile IPv6 for Service Provider Wi-Fi Deployments Byju Pularikkal Rajeev Koodli Sri Gundavelli.
DEV336. demo HTTP Packet Trace GET / HTTP/1.1 Accept: text/html, application/xhtml+xml, */* Accept-Language: en-US User-Agent: Mozilla/5.0 (compatible;
J. Halpern (Ericsson), C. Pignataro (Cisco)
IETF SFC active drafts PRESENTER: VU ANH VU
Draft-fm-bess-service-chaining-01 Prague, July 2015 Rex Fernando Stuart Mackie Dhananjaya Rao Bruno Rijsman Maria Napierala.
IETF 85 Use cases for MAP-T draft-maglione-softwire-map-t-scenarios-01 R. Maglione.
Hypertext Transfer Protocol (HTTP) COMP6218 Web Architecture Dr Nicholas Gibbins –
Network Hardware for Expanding Network
ODL SFC, Implementing IETF SFC November 14, 2016
NDN Messages and NDN Packets
S. Gundavelli, J. Korhonen, M. Liebsch, P. Seite, H. Yokota,
An MPLS-Based Forwarding Plane for Service Function Chaining
Debashish Purkayastha, Dirk Trossen, Akbar Rahman
Service Function Chaining-Enabled
On Scalability of In-Situ OAM draft-song-ippm-ioam-scalability-01
Carlos J. Bernardos, Alain Mourad, Akbar Rahman
NSH context header allocation for Mobility
IETF 100, November 2017 Singapore
Consideration of IPv6 Encapsulation for Path Services draft-li-6man-ipv6-sfc-ifit-00 Zhenbin Li, Shuping Peng.
draft-guichard-sfc-nsh-sr-02
An MPLS-Based Forwarding Plane for Service Function Chaining
Data plane round-table Feedback
Geneve applicability for service function chaining draft-boutros-nvo3-geneve-applicability-for-sfc-02 Sami Boutros Dharma Rajan Philip Kippen Pierluigi.
Tokyo OpenStack® Summit
ATIS IIF Use Cases and Relevance to CDNI
Presentation transcript:

Metadata Considerations draft-rijsman-sfc-metadata-considerations-00 Service Function Chaining Working Group IETF 89 - London - March 2014 Authors: Bruno Rijsman, Jerome Moisand Presenter: Ross Callon

2 Presented at IETF London 2014 SERVICE FUNCTION CHAINING ABSTRACTIONS IETF SERVICE FUNCTION CHAINING (SFC) WORKGROUP SFN SFI SFN SFI SFN SFI SFN SFI SFN SF SC Service Classifier Service Function Service Function Node Service Function Instance SFI SC Service Chain SP Service Path SPS Service Path Segment

3 Presented at IETF London 2014 WHAT IS METADATA? Metadata is "data about data" SFN SFI SFN SFI SFN SFI SC data Data in flow 1 metadata Metadata about flow 1 metadata Metadata about flow 2 Data in flow 2

4 Presented at IETF London 2014 METADATA USE CASE 1: SUBSCRIBER-AWARENESS CONTEXTUAL INFORMATION WHICH IS NOT LOCALLY AVAILABLE SFN SFI SFN SFI data Data Metadata data Per subscriber accounting and billing accounting-id PGW PCRF SC

5 Presented at IETF London 2014 METADATA USE CASE 2: APPLICATION-AWARENESS AVOID REPETITION OF EXPENSIVE OPERATION (E.G. DPI) SFN SFI data Data Metadata data Deep Packet Inspection (DPI) application-id SFN SFI Application-aware services No need to re-apply DPI

6 Presented at IETF London 2014 METADATA USE CASE 3: FINE-GRAINED POLICIES SUPPORT FINE-GRAINED POLICIES WITHOUT NEEDING MANY CHAINS SFN SFI SFN SFI data Data Metadata data One chain with fine-grained policies bandwidth-cap = 34 Mbps BNG RADIUS SC data Data Metadata data bandwidth-cap = 17 Mbps

7 Presented at IETF London 2014 METADATA SIGNALING - ARCHITECTURAL OPTIONS SFN SFI SFN SFI metadatadata Option 1: In-band marking Attach metadata to each packet SFN SFI SFN SFI data GET / HTTP/1.1 Host: Connection: keep-alive Cache-Control: max-age=0 Accept: text/html,application/xhtml+xml User-Agent: Mozilla/5.0 (Windows NT 6.1) Accept-Encoding: gzip,deflate Accept-Language: en-US,en;q=0.8 Metadata-Subscriber-ID: Metadata-Session-ID: HTTP Request metadata Option 2: Application Layer Headers E.g. HTTP extension headers

8 Presented at IETF London 2014 METADATA SIGNALING - ARCHITECTURAL OPTIONS SFN SFI SFN SFI data Data plane data plane control plane data plane control plane Control plane metadata Option 3: Congruent Out-of-Band Signaling Option 4: Non-Congruent Out-of-Band Signaling SFN SFI SFN SFI data Control Plane: Metadata Signaling metadata

9 Presented at IETF London 2014 METADATA SIGNALING - ARCHITECTURAL OPTIONS Option 5: Hybrid: In-Band Session-ID + Out-of-Band Signaling session-iddata SFN SFI SFN SFI data plane control plane data plane control plane Data plane Control plane session-id  metadata mapping

10 Presented at IETF London 2014 METADATA CHALLENGES Support for metadata-unaware service function Preserving metadata through metadata-unaware service functions Metadata encoding (fixed length versus TLV) Availability and performance of the control plane Synchronization between the control plane and the data plane Distributing metadata only to interested service functions Associating data plane flow with control plane signaling Layering considerations (separate path layer and service layer) Load balancing and symmetry High availability Geographic dispersion Multiple sources of metadata Extensibility

11 Presented at IETF London 2014 CONCLUSIONS Need standardization for multi-vendor interoperability Multiple approaches  In-band marking  Out-of-band signaling (congruent or non-congruent)  Hybrid approach Many challenges with each approach No single approach is obvious winner  Different approaches for different use cases?  Hybrid approach good match for mobile and fixed broadband Keep service path signaling and metadata signaling separate  Separate layers, separate headers, separate protocols  Don't need to be standardized at the same time