Subject: [sfc] TR: New Version Notification for draft-rebo-sfc-nsh-integrity-03.txt

From: <[email-masked]>
Date: Fri, 31 Jan 2020 10:11:45 +0000

Hi all, 

We prepared an updated version of the draft to take into account the comments received so far (from Tal and Daniel, in particular). The main changes are: 

* More compact format: abandon the use of separate TLVs for timestamp and key id. 
* Add a new section following the timestamp template suggested by Tal.
* Add a discussion to clarify to what extent the proposal solves the attacks discussed in draft-nguyen-sfc-security-architecture

Daniel raised a comment about the use of AES-GCM + HAMC but this may have some implications (CPU, additional 128 bit). We are planning to share the draft on the saag mailing list to have more feedback. 

Please review and share your comments. 

Cheers,
Med

-----Message d'origine-----
De : [email-masked] [mailto:[email-masked]] 
Envoyé : vendredi 31 janvier 2020 11:03
À : Dan Wing; Tirumaleswar Reddy; Tirumaleswar Reddy.K; BOUCADAIR Mohamed TGI/OLN
Objet : New Version Notification for draft-rebo-sfc-nsh-integrity-03.txt

A new version of I-D, draft-rebo-sfc-nsh-integrity-03.txt
has been successfully submitted by Mohamed Boucadair and posted to the
IETF repository.

Name:		draft-rebo-sfc-nsh-integrity
Revision:	03
Title:		Integrity Protection for Network Service Header (NSH) and Encryption of Sensitive Context Headers
Document date:	2020-01-31
Group:		Individual Submission
Pages:		28
URL:            https://www.ietf.org/internet-drafts/draft-rebo-sfc-nsh-integrity-03.txt
Status:         https://datatracker.ietf.org/doc/draft-rebo-sfc-nsh-integrity/
Htmlized:       https://tools.ietf.org/html/draft-rebo-sfc-nsh-integrity-03
Htmlized:       https://datatracker.ietf.org/doc/html/draft-rebo-sfc-nsh-integrity
Diff:           https://www.ietf.org/rfcdiff?url2=draft-rebo-sfc-nsh-integrity-03

Abstract:
   This specification adds integrity protection and optional encryption
   of sensitive metadata directly to Network Service Headers (NSH) used
   for Service Function Chaining (SFC).

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