Re: [Tsv-art] [Softwires] Tsvart last call review ofdraft-ietf-softwire-mesh-multicast-22

Joe Touch <touch@strayalpha.com> Sun, 16 September 2018 17:28 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 234AF129619; Sun, 16 Sep 2018 10:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
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 Gj8M4ZgvBwWs; Sun, 16 Sep 2018 10:28:12 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 3BC35120072; Sun, 16 Sep 2018 10:28:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Content-Type:Mime-Version:Subject:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=HpGWb5mki+CO04aeFglHs3yTVaqm+G+zLpHRqeZBMrE=; b=vbYtZUqTV/Gjt6Ihlhyk4ixw6 LKJDs9KtYm6Kx28HFa1hNiBXEuY7N1QxkFc3SDTRZjElGq2Jk5GQXszKoLXGLdsASwGaxko4rCm3t /kR1WIBe8ufXFIfK+z7pxPtBgYvrV02mqoMiSLj7Ac2yRM9ey/JvJ5lJv27c2/aUW+PKnFEJlkLX2 uWZ4yek8V2yYKxSKr6OWZyt20poUox043VRS5E9uiYeNoUFrIfJt8rVsb9mrakobUBQJPu+jhDdMW M0Qordd6+EFhkBos9AD5WpicJpwW0I5TdkpP00vcTiRxZk/CXm4V8aPBhNh1Jf8OvEY84KWMuS8lF l1zzCo7mQ==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:54079 helo=[192.168.1.77]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <touch@strayalpha.com>) id 1g1aq1-000MER-HL; Sun, 16 Sep 2018 13:28:10 -0400
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_2762C876-F302-4A2D-B064-ACF73C7D3C91"
From: Joe Touch <touch@strayalpha.com>
X-Priority: 3
In-Reply-To: <tencent_780DA8CB0F3EF600533B7D45@qq.com>
Date: Sun, 16 Sep 2018 10:27:58 -0700
Cc: tsv-art <tsv-art@ietf.org>, softwires <softwires@ietf.org>, ietf <ietf@ietf.org>, "draft-ietf-softwire-mesh-multicast.all" <draft-ietf-softwire-mesh-multicast.all@ietf.org>
Message-Id: <7DF1630D-9147-499E-A989-6B403036CD24@strayalpha.com>
References: <153612222105.14129.11979247184090243326@ietfa.amsl.com> <tencent_780DA8CB0F3EF600533B7D45@qq.com>
To: =?utf-8?B?5p2o5pyv?= <yangshu@oudmon.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-0.5
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/a2s2qUWPmQ2an9_MYJbPL097Vy4>
Subject: Re: [Tsv-art] [Softwires] Tsvart last call review ofdraft-ietf-softwire-mesh-multicast-22
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Sep 2018 17:28:14 -0000


> On Sep 15, 2018, at 11:40 AM, 杨术 <yangshu@oudmon.com> wrote:
> 
> Thank you for your useful advices, we add draft-ietf-intarea-tunnel  as a reference
> for fragment technology and ttl configuration. 
> 
> We have uploaded a new version: https://datatracker.ietf.org/doc/html/draft-ietf-softwire-mesh-multicast-23 <https://datatracker.ietf.org/doc/html/draft-ietf-softwire-mesh-multicast-23>
> 
> Best Regards,
> 
> Shu Yang

Some suggestions:

TTL:
- should refer to “TTL or hop count” (IPv6 calls this hop count because it no longer intends to reflect time, as was originally intended for IPv4)
- upon encapsulation, the outer header TTL/hopcount should be set by policy (not technology), i.e., “as desired”
- upon decapsulation, the inner header TTL/hopcount should be modified by policy as well. it might be useful to suggest that the inner one never be incremented and that it might be decremented to reflect the cost of tunnel forwarding, but it need not be modified at all

Fragmentation:
I’ve never seen “COULD” used this way and it’s incorrect. They ARE described in that draft.
It would be more correct, IMO, to say:

          The specific requirements for	
 	   fragmentation and tunnel configuration SHOULD follow the recommendations in
 	   [I-D.ietf-intarea-tunnels].

Joe