IETF Logo Mail Archive

Re: [Idr] recap my questions and issues raised during IDR Thurs session for draft-ietf-idr-tunnel-encaps-12

Srihari Sangli <ssangli@juniper.net> Wed, 12 June 2019 17:33 UTC

Return-Path: <ssangli@juniper.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2070120203; Wed, 12 Jun 2019 10:33:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level:
X-Spam-Status: No, score=-2.709 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 IbUhebYLqswM; Wed, 12 Jun 2019 10:33:31 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 63B431201F2; Wed, 12 Jun 2019 10:33:31 -0700 (PDT)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x5CHTjTu010524; Wed, 12 Jun 2019 10:33:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=Y+xmz3zAvTJRtpt+/0XmM84m2MnzEAckGKJ2BaeSnB4=; b=RR+9CUmxmIdIP+7xiVuBZ8vAW7uA3mhkQTiR7dRs8vnmkFVn5yAhAvgyPmeu/mP0YtUg Rcv+kvp0FO4e1F5j3y5Mb5GZa1MGN/TeSOi1zViga/5w01Z1R8CMWz6pZngdMLPv5/aX XKMT1wIve4YJMhH+PsV/Wq2t8HpgAbgl2CkRw7+xv05epsyf/p0wIavHC/Pxd4cBvsGd 4+047zfb0MZif8NiOwK9PG+F+ZqKV/0TgzEcG/gVWkWTdmzp3g61B8rumTjSNlgw3S+Y FIgqg6R9YYfVtN/4XCdDGbmGQS/PsZrvbzTPz1xAep0Q//vHAeY5cbbOyA1sWoVlYBjM Xg==
Received: from nam03-dm3-obe.outbound.protection.outlook.com (mail-dm3nam03lp2058.outbound.protection.outlook.com [104.47.41.58]) by mx0b-00273201.pphosted.com with ESMTP id 2t32earcvf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 12 Jun 2019 10:33:25 -0700
Received: from BYAPR05MB4551.namprd05.prod.outlook.com (52.135.203.158) by BYAPR05MB5366.namprd05.prod.outlook.com (20.177.127.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.10; Wed, 12 Jun 2019 17:33:23 +0000
Received: from BYAPR05MB4551.namprd05.prod.outlook.com ([fe80::e11a:cc85:3d8d:15ca]) by BYAPR05MB4551.namprd05.prod.outlook.com ([fe80::e11a:cc85:3d8d:15ca%7]) with mapi id 15.20.1987.010; Wed, 12 Jun 2019 17:33:23 +0000
From: Srihari Sangli <ssangli@juniper.net>
To: John Scudder <jgs@juniper.net>, Keyur Patel <keyur@arrcus.com>
CC: Linda Dunbar <ldunbar@futurewei.com>, Robert Raszuk <robert@raszuk.net>, "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-tunnel-encaps@ietf.org" <draft-ietf-idr-tunnel-encaps@ietf.org>
Thread-Topic: [Idr] recap my questions and issues raised during IDR Thurs session for draft-ietf-idr-tunnel-encaps-12
Thread-Index: AdUfzDTwk+JWx4NrTbCw24feqIEcxQADfhQAAABU8AAALY6XEAAB/DuAAADA04AAGnlYgAAHy0SAAANKonD//6TtAIAAeiGAgABhFgA=
Date: Wed, 12 Jun 2019 17:33:23 +0000
Message-ID: <31706AD8-EE52-475D-AD6C-D80381303A0D@juniper.net>
References: <MN2PR13MB358247036D97F6620E2CB987A9130@MN2PR13MB3582.namprd13.prod.outlook.com> <234E41A5-F754-4630-B73C-8A9D52E44198@juniper.net> <6691B6FF-E9F5-4E9B-8D91-E8371993EDB5@juniper.net> <MN2PR13MB35826173FB5AC8D019497438A9ED0@MN2PR13MB3582.namprd13.prod.outlook.com> <5E89EE56-8852-4A1C-B072-EFE15ADA2618@juniper.net> <9E64708F-5E78-422C-8339-3447529BABB4@arrcus.com> <CAOj+MMFVhNFUnAe-QxyWHX65PY=VQmCK0N5aOcx=5nAApX5z4g@mail.gmail.com> <68538D45-E8CD-4FDA-ABA4-BEC4A7586410@juniper.net> <MN2PR13MB3582C58B3C84105B43191547A9EC0@MN2PR13MB3582.namprd13.prod.outlook.com> <F0F388CC-9B96-4E35-8E20-72A3B0C75347@arrcus.com> <900E9356-CB87-4148-BAE9-238A6C3A3230@juniper.net>
In-Reply-To: <900E9356-CB87-4148-BAE9-238A6C3A3230@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [116.197.184.14]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fbbf50ac-f3c3-4d76-6568-08d6ef5c1218
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:BYAPR05MB5366;
x-ms-traffictypediagnostic: BYAPR05MB5366:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BYAPR05MB5366F0FACCBBEB72659C70BCB9EC0@BYAPR05MB5366.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 0066D63CE6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(346002)(136003)(376002)(39860400002)(396003)(199004)(189003)(2906002)(8676002)(4744005)(3846002)(71200400001)(1941001)(71190400001)(66066001)(81166006)(6116002)(8936002)(5660300002)(81156014)(7736002)(102836004)(486006)(76176011)(446003)(66574012)(6506007)(14444005)(2616005)(256004)(99286004)(33656002)(11346002)(476003)(478600001)(53936002)(6512007)(25786009)(68736007)(316002)(36756003)(66946007)(66476007)(86362001)(6246003)(26005)(76116006)(91956017)(14454004)(66556008)(73956011)(54906003)(229853002)(6306002)(66446008)(64756008)(4326008)(54896002)(110136005)(6436002)(186003)(6486002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB5366; H:BYAPR05MB4551.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: B3i0uBpXavbG0ieNElo/mOpAyqwz4vSiUFejP9Aup3Y6zJ4nRaxqNrFQrubgejc4Zb3y6xP0WE4dcM7OqhQEPpjyBw9VhZEabvmQKzpLWRdBvWxGHErp9KLj6SGcItUBboFiz/fCknOO/mNJ/hNGqL0meUtgQDh9aOLvbHy5kC+dj9Li1+dRRIo2OG3XEVExYJCdh6H2i2bhIPymWlytny60VQTgSzYlujlNE3cvWMiFHiJN/MwVhtuetzVMArFFAOVq5tixcpIbSpI11yC0bgBJSKq9TUcGORrsthbtyJo8CXrJe8ynZKO6j6b2V+KK/t/YN39i8Cshr7Sg6cEy5g1/hUuH/JJe+JrZHwIELzR5DVEddCKopOK6BQIYQID/geknAmRiGxdgqph+T9IdQ4/TtGZaLtiIwE/rVVRcFQQ=
Content-Type: multipart/alternative; boundary="_000_31706AD8EE52475DAD6CD80381303A0Djunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: fbbf50ac-f3c3-4d76-6568-08d6ef5c1218
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jun 2019 17:33:23.7263 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ssangli@juniper.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB5366
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-12_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906120118
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3ku4LoYpga976PaPxqS8Ieca2oE>
Subject: Re: [Idr] recap my questions and issues raised during IDR Thurs session for draft-ietf-idr-tunnel-encaps-12
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2019 17:33:33 -0000

(As a contributor)

I guess the disconnect arises from how each reader parses “remote”. To me, and I guess other reviewers who also didn’t notice a problem, it is self-evident that “remote” means “the other end of the tunnel from the point of view of the router encapsulating the packet”. This conversation makes it clear that’s not the only possible reading. As mentioned earlier, I would have no objection to clarifying that point.


Srihari> Yes, that’s correct interpretation. “Remote” was referred from Tunnel endpoint perspective. thanks

—John

v2.23.0 | Report a Bug | By Email