Re: Suresh Krishnan's Yes on draft-ietf-rtgwg-enterprise-pa-multihoming-08: (with COMMENT)

Suresh Krishnan <Suresh@kaloom.com> Tue, 02 July 2019 01:48 UTC

Return-Path: <Suresh@kaloom.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABB1F12018B; Mon, 1 Jul 2019 18:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kaloom.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 6cmCB4FSR_PT; Mon, 1 Jul 2019 18:48:49 -0700 (PDT)
Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670135.outbound.protection.outlook.com [40.107.67.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B913712018F; Mon, 1 Jul 2019 18:48:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kaloom.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+tfNExRaGJgl6TDZvWGE7QIMjWOGABQ1Yv4lP5lUb/o=; b=Gp5rEU+HZ+U0hps7PAfImG4ixEuB9xR7QcSxlWGXzBkKn98VLTcu9sfzNDPhxjJLl+Jaddxgn/kzkbxZaC7jdmeYRxjnbUEpdsZg8pwyOOGqKXn3iv1Q2mPFLO2p6Uu5nfcYCi0h4vB+gUD07uX0iKhTF4qYlABzmnWXIt2Zs8o=
Received: from YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM (52.132.45.144) by YTOPR0101MB1131.CANPRD01.PROD.OUTLOOK.COM (52.132.50.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2032.18; Tue, 2 Jul 2019 01:48:46 +0000
Received: from YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM ([fe80::20b6:a749:45f6:12ba]) by YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM ([fe80::20b6:a749:45f6:12ba%3]) with mapi id 15.20.2032.019; Tue, 2 Jul 2019 01:48:46 +0000
From: Suresh Krishnan <Suresh@kaloom.com>
To: Jen Linkova <furry13@gmail.com>
CC: The IESG <iesg@ietf.org>, Ronald Bonica <rbonica@juniper.net>, rtgwg-chairs <rtgwg-chairs@ietf.org>, "draft-ietf-rtgwg-enterprise-pa-multihoming@ietf.org" <draft-ietf-rtgwg-enterprise-pa-multihoming@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: Suresh Krishnan's Yes on draft-ietf-rtgwg-enterprise-pa-multihoming-08: (with COMMENT)
Thread-Topic: Suresh Krishnan's Yes on draft-ietf-rtgwg-enterprise-pa-multihoming-08: (with COMMENT)
Thread-Index: AQHVMB9Bz7erwVL5OUyiROjPoS7uVKa2kFMA
Date: Tue, 2 Jul 2019 01:48:46 +0000
Message-ID: <03281068-2F7F-4075-AF00-ABBA4A8AB259@kaloom.com>
References: <156162627222.21644.1215853019054959295.idtracker@ietfa.amsl.com> <CAFU7BATvj6VunkVCE6XvqLizeUwxO8p-Zo37Qm_cSHigVGN38Q@mail.gmail.com>
In-Reply-To: <CAFU7BATvj6VunkVCE6XvqLizeUwxO8p-Zo37Qm_cSHigVGN38Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Suresh@kaloom.com;
x-originating-ip: [172.58.27.251]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8460a6b8-dba8-4384-ef74-08d6fe8f6c29
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:YTOPR0101MB1131;
x-ms-traffictypediagnostic: YTOPR0101MB1131:
x-microsoft-antispam-prvs: <YTOPR0101MB1131D6B24F65E26D95BA67E8B4F80@YTOPR0101MB1131.CANPRD01.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 008663486A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39850400004)(396003)(376002)(136003)(366004)(189003)(199004)(229853002)(508600001)(76176011)(66446008)(2906002)(33656002)(4326008)(6486002)(36756003)(1411001)(6512007)(6246003)(66574012)(25786009)(68736007)(66066001)(26005)(486006)(316002)(71190400001)(71200400001)(81156014)(91956017)(8676002)(6436002)(6116002)(7736002)(54906003)(305945005)(102836004)(76116006)(66946007)(99286004)(6916009)(73956011)(53936002)(80792005)(5660300002)(6506007)(53546011)(186003)(3846002)(11346002)(476003)(2616005)(446003)(72206003)(14454004)(66556008)(66476007)(64756008)(8936002)(86362001)(256004)(81166006); DIR:OUT; SFP:1102; SCL:1; SRVR:YTOPR0101MB1131; H:YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: kaloom.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: W4OXynNfno0KC/t/ubyIRbUm/CZwU4sEth3O1BK8snXIPrddHI2KaU2+Un1lQmMbDzVL9/F1mIBkuWuEmkJOR27pW38cs3t0WcU4FB2ed/GMDXwFp+A7wfhe+wu8OVdAD0WwL6226qsnOC6/W8tVZm4k1VFFslgeN6lTCeHaYh4OCoL/mCGS+5eJE/WFzNhrXqUjWYmKdUyZ1aCqRXs9hS0IpGIIpzUWcsq4xb6+r9QagNmeDmHXRxg86noTbe7zRc0MlRZ63TZ3fjsCGJoqEiX1ejh3SEt7W3XMqXWZTWrTdunztUIBYK3pJAXofG9BNgCME2ugarjhuRrfmafxUAFKCVvd/o9YV1XIdPjVhTHlY1PFzPTPmyq8MpBSTYZp0oBMmUl4jedd1ciRDMisGDZ95lKM17aZ6vqWZWqpJZg=
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1E1B664F2ABCC44D8305C35D7A00D2A0@CANPRD01.PROD.OUTLOOK.COM>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: kaloom.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8460a6b8-dba8-4384-ef74-08d6fe8f6c29
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jul 2019 01:48:46.7050 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 47d58e26-f796-48e8-ac40-1c365c204513
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Suresh@kaloom.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1131
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/TIRsElsINRDCfOJUN4GNyR3lDnQ>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2019 01:48:51 -0000

> On Jul 1, 2019, at 11:11 PM, Jen Linkova <furry13@gmail.com>; wrote:
> 
> On Thu, Jun 27, 2019 at 7:04 PM Suresh Krishnan via Datatracker
> <noreply@ietf.org>; wrote:
>> * Section 3.3 Paragraph 2
>> 
>> The destination address of H41 seems to be wrong. Shouldn't it be
>> "D=2001:db8:0:b020::41" instead of "D=2001:db8:0:b010::41"?
> 
> Awesome, good catch, thanks a lot! It's a typo indeed, fixed!
> 
>> 
>> * Section 4 Page 22
>> 
>> I think this text needs to be rephrased as a requirement rather than a two
>> statements.
>> 
>> "Any traffic that needs to exit the site will eventually hit a SADR-
>>   capable router.  Once that traffic enters the SADR-capable domain,
>>   then it will not leave that domain until it exits the site."
> 
> I've rephrased as
> 
> "As all SERs belong to the SADR domain any traffic that needs to exit
> 
>   the site will eventually hit a SADR-capable router.  To prevent
>   routing loops involving SADR-capable and non-SADR-capable routers,
>   traffic that enters the SADR-capable domain does not leave the domain
>   until it exits the site.  Therefore all SADR-capable routers with the
>   domain MUST be logically connected."
> 
> Is it better?
> 
>> * Section 5.2.1.
>> 
>> Not sure what the reference to RFC8415 accomplishes in this contact. Is it just
>> a pointer to DHCPv6? If so it needs to be earlier in the document. If there is
>> a more relevant reason, I think the pointer needs to be more specific (e.g. a
>> section in RFC8415).
> 
> I've moved RFC8415 reference to the first mention of DHCPv6 in the doc.
> 
>> 
>> * Section 7.3
>> 
>> I think a reference to something like RFC6824 might be useful here
> 
> Added.

Excellent Jen. All these text changes look good. Thanks for addressing my concerns.

Regards
Suresh