Re: [Rtg-dt-encap-considerations] Added Hardware Friendly to Dallas slides

Erik Nordmark <nordmark@sonic.net> Wed, 11 March 2015 23:18 UTC

Return-Path: <nordmark@sonic.net>
X-Original-To: rtg-dt-encap-considerations@ietfa.amsl.com
Delivered-To: rtg-dt-encap-considerations@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB181A8941 for <rtg-dt-encap-considerations@ietfa.amsl.com>; Wed, 11 Mar 2015 16:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZDmXNsypKuA for <rtg-dt-encap-considerations@ietfa.amsl.com>; Wed, 11 Mar 2015 16:18:30 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 794731A893F for <Rtg-dt-encap-considerations@ietf.org>; Wed, 11 Mar 2015 16:18:30 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t2BNIRjP019050 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 11 Mar 2015 16:18:28 -0700
Message-ID: <5500CD43.5080107@sonic.net>
Date: Wed, 11 Mar 2015 16:18:27 -0700
From: Erik Nordmark <nordmark@sonic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Larry Kreeger (kreeger)" <kreeger@cisco.com>, "rtg-dt-encap-considerations@ietf.org" <Rtg-dt-encap-considerations@ietf.org>
References: <54FF985E.2070608@sonic.net> <D12610B4.13BCFE%kreeger@cisco.com>
In-Reply-To: <D12610B4.13BCFE%kreeger@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Sonic-CAuth: UmFuZG9tSVbuK0YJu5a1/ul5llJddePFxTlRZGZiMb2eiEtE+NtJHoCi4HaxUi5Eanx/A0YLhHCoPG60R9jp88kpCOE1Qkk0
X-Sonic-ID: C;vHiG7ETI5BGe/75YxQPdhw== M;uGac7ETI5BGe/75YxQPdhw==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-dt-encap-considerations/4eBKvigUnmkqRep2KJV34nsvEQY>
Subject: Re: [Rtg-dt-encap-considerations] Added Hardware Friendly to Dallas slides
X-BeenThere: rtg-dt-encap-considerations@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Design Team on Encapsulation Considerations discussion list <rtg-dt-encap-considerations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dt-encap-considerations>, <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/>
List-Post: <mailto:rtg-dt-encap-considerations@ietf.org>
List-Help: <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dt-encap-considerations>, <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2015 23:18:37 -0000

On 3/11/15 3:47 PM, Larry Kreeger (kreeger) wrote:
> Hi Erik,
>
> Here are my comments on the slides.  I don't know if the hardware friendly
> slide will stimulate more discussion than several other points in these
> slides, so I don't see why not to have it.
OK, I've added the slide to the NVO3 set for now.
>
> Slide 7: I'm not sure what the bullet "Perhaps optional OAM info modified
> along path?" means.
This was a vague reference to timestamps etc for OAM purposes. I've 
reworded it to be more specific.
> Also, SFC allows not only the service path info to be
> carried (and modified), but the service metadata may also be modified.
Is " *Service meta-data may be modified by service functions" a correct 
state*ment?**
>
> Slide 9: It isn't clear to me whether limiting the source port entropy to
> only use the ephemeral port range is required.  I think in many cases it
> will be fine to use all 16 bits of source port.
The document doesn't even specify exactly why, but has some more text.
If there is some middlebox, it might look at the UDP source port. For 
instance, UDP source ports used by known insecure protocols might be 
blocked by a firewall. If all 16 bits are used that means some flows 
would get blocked. But in other deployments all bits can be used.

How about I have the slide say ">=14 bits" and we can talk to this point?
>
> Slide 13: The bullet "Use some 'discard' next header value?" is one
> option, but it eliminates the possibility of carrying a payload snippet
> before the OAM message.  The other option is an explicit OAM bit (which
> several headers have).
I've reworded as
*Use some “discard” next header value, or OAM bit?

*Note that I'm not sure the discussed OAM bit means the same to everybody.**
>
> Slide 18: Loose -> Lose
Fixed.
>
> Slide 24: Why is there a question mark after "WG document"?  We already
> have a document.  Maybe this is to remind you to put the draft name?
The DT output is a personal document. I don't know (and haven't asked 
Alia) whether her intent was to have the RTGWG pick this up as a WG 
document and review it. Hence asking the question.

I made it a bit more clear:
*RTGWG WG document? Or somewhere else?

*Thanks for your review.

Erik

**
>
>   - Larry
>
>
>
>
>
> On 3/10/15 6:20 PM, "Erik Nordmark" <nordmark@sonic.net> wrote:
>
>> See
>> https://docs.google.com/a/aristanetworks.com/presentation/d/1r_LpKB0tV8VJV
>> Jx-t3h3NJagRCtIxqFXS8JesV9BCOo/edit?usp=sharing
>>
>> First question is whether we agree on this summary (I did it from memory)
>> Second question is whether we should add the Hardware Friendly slide to
>> the NVO3 slides for this Friday's presentation?
>> It might raise some discussion.
>>
>>     Erik
>>
>> _______________________________________________
>> Rtg-dt-encap-considerations mailing list
>> Rtg-dt-encap-considerations@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtg-dt-encap-considerations
>