Subject: [sfc] New Version Notification for draft-sarikaya-sfc-hostid-serviceheader-05.txt

From: Behcet Sarikaya <[email-masked]>
Date: Thu, 20 Jul 2017 07:34:43 -0500

Folks,
We submitted a keep-alive revision of our hostid service header draft as
follows.
If you have any comments please post them on the list.

Regards,

Behcet

On Thu, Jul 20, 2017 at 7:30 AM, <[email-masked]> wrote:

>
> A new version of I-D, draft-sarikaya-sfc-hostid-serviceheader-05.txt
> has been successfully submitted by Behcet Sarikaya and posted to the
> IETF repository.
>
> Name:           draft-sarikaya-sfc-hostid-serviceheader
> Revision:       05
> Title:          Service Function Chaining Service, Subscriber and Host
> Identification Use Cases and Metadata
> Document date:  2017-07-20
> Group:          Individual Submission
> Pages:          17
> URL:            https://www.ietf.org/internet-drafts/draft-sarikaya-sfc-
> hostid-serviceheader-05.txt
> Status:         https://datatracker.ietf.org/
> doc/draft-sarikaya-sfc-hostid-serviceheader/
> Htmlized:       https://tools.ietf.org/html/draft-sarikaya-sfc-hostid-
> serviceheader-05
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-sarikaya-sfc-
> hostid-serviceheader-05
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-sarikaya-sfc-
> hostid-serviceheader-05
>
> Abstract:
>    This document discusses considerations related to passing service-,
>    host- and subscriber-related information to upstream Service
>    Functions for the sake of policy enforcement and appropriate SFC-
>    inferred forwarding.  Once the information is consumed by SFC-aware
>    elements of an SFC-enabled domain, the information is stripped from
>    packets so that privacy-sensitive information is not leaked outside
>    an SFC-enabled domain.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>