Re: [Isis-wg] [Technical Errata Reported] RFC5309 (5007)

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Thu, 15 June 2017 07:11 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D44031294EE for <isis-wg@ietfa.amsl.com>; Thu, 15 Jun 2017 00:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.59
X-Spam-Level:
X-Spam-Status: No, score=-4.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=eci365.onmicrosoft.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 1DEWlPYXOTNx for <isis-wg@ietfa.amsl.com>; Thu, 15 Jun 2017 00:11:54 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.143]) (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 78D2A1270A7 for <isis-wg@ietf.org>; Thu, 15 Jun 2017 00:11:53 -0700 (PDT)
Received: from [85.158.136.83] by server-7.bemta-5.messagelabs.com id 37/8C-02181-73332495; Thu, 15 Jun 2017 07:11:51 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1WTWUwTURSGvZ3OgmH0AirHCkSqRtQUaXCZxLg RY2oUVIwPGrcBR9rYFtKppvpgiAKJrRElBBHRSkQFEVTcEUExGAS34hI3jCgPiAsoKiAWnenU bZ6+c////OfM5A5DBHdSGkZw2AWblTdrqcHqKaPOOXT62LgVMbkDk7jPrc0E5+07j7i8s9cJ7 oHTRXOnf5yhuesN6QRXX9dJcnerKW577VdqToDhbXYhMrxsOaIy5PafIQ2XC1pow+uLaw3FxX 0qQ3rWTXIJvZI0WZNSHetIo+vByLSePsZx49sAnY56OxgnGsyocRYBP5rz1XIRjHNUUPTxqMq JAqTiFYL+zK0yU3gmVJa1UDIPw8sgr81Lyw0ELlVBk3eHTwjBc2H3see0YooDd9dtQuFt8LSn hpRZjcfBu85nEjMMi1fBroxkZbCTggM1bb6cALwUjjprfX6ER0BP40nfQgQOhWdtbh8DxlBcf Y9QeDi8fTPg97sQXDk8SzmPhPyXhbTC4dDsdiF5GOBdBOS0n/Y3T4T8qjx/aDw0dA8geTnAY+ Bc+2rFL2XuO5Th92+E4ton/qAKBB8q9lFK0URC+YVWvysMMrMP+bmKhq4Gu/KJNNDycCdSOAz aX1wl96Cogn/eTmErPPZUUzKzOAhu7W9TF0hLEXgCnKqarFgiIdfVSiscBZmFB+l/zw8j+gSK EgXbZsGm00+PTrKZUox2C28y6/QxU6MtgijyKYKZTxKjk1MtlUi6iIOk5xLyNC2oQyMZlXY4O zQibkXwkKTU9VuMvGhca9tkFsQ6FMYwWmB79ZIWZBNSBMcGk1m6zb9lYAK1w9jpMZLMimm8RT SlKFIjitSEso1yH5YF4ybrn7bf/0EzCteEsEhaJDgwTbBZTPb/9Q4UyiBtCOuOllICTVb7n/Q OabBKGpx4f4482M7/lTTpyDPt6bz6hK41M0Yle8Z9K5lRHpQxPm5mVf1sffwir7MsTVfmPa4v erQtNsFTvlf7/aGulOrdWjKaCO8OnHT8Z/8XMnLIncrP2UsW7829VmK6G7suYkt4d04r2Z5Xr 3XlL8p6tVz9KeD9fKiJT3hRuqxo4djLyNoQ8cGdM+/S8sTYTqxVi0ZeP5Gwifwvv2/HgQIEAA A=
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-2.tower-36.messagelabs.com!1497510701!111068683!1
X-Originating-IP: [52.27.180.120]
X-StarScan-Received:
X-StarScan-Version: 9.4.19; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 3544 invoked from network); 15 Jun 2017 07:11:44 -0000
Received: from ec2-52-27-180-120.us-west-2.compute.amazonaws.com (HELO EUR02-VE1-obe.outbound.protection.outlook.com) (52.27.180.120) by server-2.tower-36.messagelabs.com with AES256-SHA256 encrypted SMTP; 15 Jun 2017 07:11:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector1-ecitele-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=zMJr/ykeyu2BrKqpr2LttfCx49Y4VrFUbEoqE8H62/Y=; b=FkaMycNFUuL5JxfghfVFk73TXwi3PZQVHRDXlHZOJa7bU5JvPwS6QkaA1XcMF98kKCWb/a6yF7FNgOOrLSXQz99piTmitBt6Y0v77mQakvUFUEaJdw45xjTRvLtXpdaKHDYYhcrVVgUwyo0Rz3i92xMfjO8jSFuDNpFP1VNEOC8=
Received: from AM4PR03MB1713.eurprd03.prod.outlook.com (10.167.88.15) by AM4PR03MB1715.eurprd03.prod.outlook.com (10.167.88.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1157.12; Thu, 15 Jun 2017 07:11:39 +0000
Received: from AM4PR03MB1713.eurprd03.prod.outlook.com ([fe80::7971:7fe2:9bc5:446a]) by AM4PR03MB1713.eurprd03.prod.outlook.com ([fe80::7971:7fe2:9bc5:446a%14]) with mapi id 15.01.1157.017; Thu, 15 Jun 2017 07:11:39 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Alia Atlas <akatlas@gmail.com>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
CC: Hannes Gredler <hannes@gredler.at>, "Naiming Shen (naiming)" <naiming@cisco.com>, "isis-wg@ietf.org" <isis-wg@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>, "db3546@att.com" <db3546@att.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "chopps@chopps.org" <chopps@chopps.org>
Thread-Topic: [Isis-wg] [Technical Errata Reported] RFC5309 (5007)
Thread-Index: AQHSwYoCxBhcZtgLd0CoSDR/tVhrP6Hd9k4AgAAWr1CAALaTgIAAU2fwgAYrFwCAAx8rkIA7MMiAgAEH4ACAACCZAIAAK26AgAABeACAAOJ4QA==
Date: Thu, 15 Jun 2017 07:11:39 +0000
Message-ID: <AM4PR03MB17136399FC49B4C4AC15EF669DC00@AM4PR03MB1713.eurprd03.prod.outlook.com>
References: <20170430081555.026C1B8183C@rfc-editor.org> <bd426412060143b18b888f9fb9135728@XCH-ALN-001.cisco.com> <AM4PR03MB171368B3A0BC936159ABE14A9D150@AM4PR03MB1713.eurprd03.prod.outlook.com> <F45DED94-22FE-436D-A2E9-AD01AB454832@cisco.com> <AM4PR03MB171381904BE473010383FAD89D140@AM4PR03MB1713.eurprd03.prod.outlook.com> <5C8FC259-C018-4542-B77D-F23BC3E212A9@cisco.com> <HE1PR03MB1722501D2C6E614E8551AD319DE90@HE1PR03MB1722.eurprd03.prod.outlook.com> <CAG4d1reBKcwk0UZVvQgOoLhWramwcqtjPOXegcg5ubnRJsOkiQ@mail.gmail.com> <6c75a3bb-4a00-f0b7-861a-1fbd4496964e@gredler.at> <CAG4d1rcPAS2GdcR0ZSi5RVpQkfi1b0iGuxytygEXjKdTNVNNxw@mail.gmail.com> <64254d6f9a8540bd82842d29a0136e67@XCH-ALN-001.cisco.com> <CAG4d1rd+9Do-s7tvBaeY29RwajAP5FCfFQtXF6C4yTb4hc1TkA@mail.gmail.com>
In-Reply-To: <CAG4d1rd+9Do-s7tvBaeY29RwajAP5FCfFQtXF6C4yTb4hc1TkA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.241.1]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM4PR03MB1715; 7:OR/y3lwnDgSOZNQXNmVdnLXAZy2Ye1+IqPq4fT3p+Uxqj3fWtUuGmynFTgOZUa21U8Uuc00gPfntQD1L4qNia7DkFB5OZd4HJn9sP8WjPscukGcfaW+tEZxd/3v44D5JxC65Gq3KFfIZecfMTZ2NqJTjFMwoqATA/Cmd6ADbwhh/zB6VoCE7V/Gy0moiHymdnIWAtEcvVfCq0LdgtdMJbJpfAicxm2vosqLeG/2WyVk1LJ3tffUNE6IehdnBE/COLuu0DHvAfx7+BHfV2Vwz1HhB0BXIjX3oySEtJCkFy8vnkCwOew1BaujDcDpxZPzQgS1F7NZddfcSUY0h78qPTg==
x-ms-traffictypediagnostic: AM4PR03MB1715:
x-ms-office365-filtering-correlation-id: 4f8da24b-cdcd-4446-8c9d-08d4b3bdc4e8
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:AM4PR03MB1715;
x-microsoft-antispam-prvs: <AM4PR03MB1715E79E2347ED79DC97B5519DC00@AM4PR03MB1715.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278428928389397)(97927398514766)(100405760836317)(95692535739014)(58145275503218)(21748063052155)(279101305709854)(142525466485115);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(100000703101)(100105400095)(10201501046)(6055026)(6041248)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123558100)(20161123555025)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM4PR03MB1715; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM4PR03MB1715;
x-forefront-prvs: 0339F89554
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6019001)(39410400002)(39850400002)(39860400002)(39450400003)(39840400002)(39400400002)(269900001)(24454002)(13464003)(252514010)(377454003)(85664002)(51914003)(16200700003)(99286003)(5890100001)(189998001)(54356999)(33656002)(54906002)(14454004)(5250100002)(72206003)(86362001)(575784001)(6306002)(478600001)(5660300001)(55016002)(54896002)(966005)(2906002)(76176999)(38730400002)(2900100001)(50986999)(81166006)(7736002)(6246003)(74316002)(9686003)(93886004)(236005)(7906003)(6506006)(6436002)(790700001)(39060400002)(606005)(4326008)(7696004)(2950100002)(229853002)(8676002)(66066001)(3846002)(3660700001)(53946003)(53546009)(8936002)(19609705001)(53936002)(16799955002)(6116002)(3280700002)(102836003)(25786009)(15188155005)(19273905006)(579004)(559001)(569005); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4PR03MB1715; H:AM4PR03MB1713.eurprd03.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR03MB17136399FC49B4C4AC15EF669DC00AM4PR03MB1713eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jun 2017 07:11:39.9535 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR03MB1715
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/agfnWMC154MAOMGyKbyf-j9DpSs>
Subject: Re: [Isis-wg] [Technical Errata Reported] RFC5309 (5007)
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jun 2017 07:12:00 -0000

Alia, Les and all,
The note proposed by Les looks OK to me.

Regards,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com

From: Alia Atlas [mailto:akatlas@gmail.com]
Sent: Wednesday, June 14, 2017 8:40 PM
To: Les Ginsberg (ginsberg) <ginsberg@cisco.com>
Cc: Hannes Gredler <hannes@gredler.at>at>; Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>om>; Naiming Shen (naiming) <naiming@cisco.com>om>; isis-wg@ietf.org; RFC Errata System <rfc-editor@rfc-editor.org>rg>; db3546@att.com; Alvaro Retana (aretana) <aretana@cisco.com>om>; chopps@chopps.org
Subject: Re: [Isis-wg] [Technical Errata Reported] RFC5309 (5007)

Les,

Thanks!   I'll let this sit for a day or so to see if there are more comments
and then reject the errata with this note.

Regards,
Alia

On Wed, Jun 14, 2017 at 1:34 PM, Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>> wrote:
Alia –

Try this:

“RFC 5309 introduced the possibility of supporting an unnumbered configuration on a LAN. Statements in this RFC regarding ARP concerns are therefore deliberately limited to this new configuration.

For IS-IS, RFC 3787 Section 10 discusses concerns regarding mismatched subnets on numbered links.

For OSPF it is well known that there are some existing implementations which have supported mismatched subnets for many years.

Any concerns with ARP behavior  in support of mismatched subnets on numbered LANs is out of scope of RFC 5309.”

   Les


From: Alia Atlas [mailto:akatlas@gmail.com<mailto:akatlas@gmail.com>]
Sent: Wednesday, June 14, 2017 7:59 AM
To: Hannes Gredler
Cc: Alexander Vainshtein; Naiming Shen (naiming); Les Ginsberg (ginsberg); isis-wg@ietf.org<mailto:isis-wg@ietf.org>; RFC Errata System; alex.zinin@alcatel-lucent.com<mailto:alex.zinin@alcatel-lucent.com>; db3546@att.com<mailto:db3546@att.com>; Alvaro Retana (aretana); chopps@chopps.org<mailto:chopps@chopps.org>
Subject: Re: [Isis-wg] [Technical Errata Reported] RFC5309 (5007)

On Wed, Jun 14, 2017 at 9:02 AM, Hannes Gredler <hannes@gredler.at<mailto:hannes@gredler.at>> wrote:
hi alia,

the issue at hand IMO does not warrant an errata.

this is more related to how ARP & nexthop handling
is performed internally in a routing-stack which is IMO a bit outside
of what isis-wg should work on.

I agree that it is a bit outside the scope - but the issue comes up
from interactions.   I am happy to reject the errata, if that is the
consensus, but I could use a clearly written note explaining why.
I'm also fine with having it become an advisory note; I think it is
useful to provide non-normative guidance.

Regards,
Alia



/hannes

On 6/13/17 23:18, Alia Atlas wrote:
> Chris, Hannes, Les, Sasha,
>
> Is there a conclusion about this Errata report?
>
> From the discussion, it sounds like there is a problem and the argument
> is about
> what layer it should be handled by.  Perhaps, instead of normative text,
> it could be
> a note?
>
> Regards,
> Alia
>
> On Sun, May 7, 2017 at 1:35 AM, Alexander Vainshtein
> <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
> <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>> wrote:
>
>     Naiming,____
>
>     Lots of thanks for a very detailed response.____
>
>     __ __
>
>     I fully agree with you that reasonable ARP implementations
>     (including Linux) provide for enabling or disabling the check of the
>     source IP address. ____
>
>     I also agree that disabling this check on unnumbered P2P-over-LAN
>     interfaces is the most useful use case when this check must be
>     disabled.____
>
>     __ __
>
>     I also agree that the if a pair of connected interfaces are
>     configured with IP addresses from mismatched subnets, traffic would
>     not pass unless ARP check is relaxed for both LAN and P2P
>     interfaces. My point is that, in the case of OSPF, if the interfaces
>     were not configured as P2P, */an OSPF adjacency would not be
>     formed/*. Therefore the link would not be part of the network graph
>     and not taken into account in the OSPF routes computation. ____
>
>     __ __
>
>     But if these interfaces are configured as P2P for OSPF, an adjacency
>     is formed and it reaches its FULL state. The result is blackholing,
>     and RFC 5309 neither instructs the operators to avoid such
>     configuration nor requires from the implementations to relax the ARP
>     check.____
>
>     __ __
>
>     Regards,____
>
>     Sasha____
>
>     __ __
>
>     Office: +972-39266302<tel:%2B972-39266302> <tel:+972%203-926-6302>____
>
>     Cell:      +972-549266302<tel:%2B972-549266302> <tel:+972%2054-926-6302>____
>
>     Email:   Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
>     <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>____
>
>     __ __
>
>     *From:*Naiming Shen (naiming) [mailto:naiming@cisco.com<mailto:naiming@cisco.com>
>     <mailto:naiming@cisco.com<mailto:naiming@cisco.com>>]
>     *Sent:* Friday, May 05, 2017 8:44 AM
>
>
>     *To:* Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
>     <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>>
>     *Cc:* Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>
>     <mailto:ginsberg@cisco.com<mailto:ginsberg@cisco.com>>>; isis-wg@ietf.org<mailto:isis-wg@ietf.org>
>     <mailto:isis-wg@ietf.org<mailto:isis-wg@ietf.org>>; RFC Errata System
>     <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org> <mailto:rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>>;
>     alex.zinin@alcatel-lucent.com<mailto:alex.zinin@alcatel-lucent.com>
>     <mailto:alex.zinin@alcatel-lucent.com<mailto:alex.zinin@alcatel-lucent.com>>; akatlas@gmail.com<mailto:akatlas@gmail.com>
>     <mailto:akatlas@gmail.com<mailto:akatlas@gmail.com>>; db3546@att.com<mailto:db3546@att.com> <mailto:db3546@att.com<mailto:db3546@att.com>>;
>     Alvaro Retana (aretana) <aretana@cisco.com<mailto:aretana@cisco.com>
>     <mailto:aretana@cisco.com<mailto:aretana@cisco.com>>>; chopps@chopps.org<mailto:chopps@chopps.org>
>     <mailto:chopps@chopps.org<mailto:chopps@chopps.org>>; hannes@gredler.at<mailto:hannes@gredler.at> <mailto:hannes@gredler.at<mailto:hannes@gredler.at>>
>     *Subject:* Re: [Isis-wg] [Technical Errata Reported] RFC5309 (5007)____
>
>     __ __
>
>     __ __
>
>     Sasha,____
>
>     __ __
>
>     Thanks for the comments.____
>
>     __ __
>
>     In OS implementations, in particular linux, there are various
>     releases and____
>
>     configure options, so it varies quite a bit for ARP. This pointer
>     shows how to change____
>
>     the ARP behavior on linux:____
>
>     __ __
>
>     http://kb.linuxvirtualserver.org/wiki/Using_arp_announce/arp_ignore_to_disable_ARP
>     <http://kb.linuxvirtualserver.org/wiki/Using_arp_announce/arp_ignore_to_disable_ARP>____
>
>     __ __
>
>     For example, the variable ‘arp_ignore’, has the code sample in
>     ‘arp.c’:____
>
>     http://elixir.free-electrons.com/linux/latest/source/net/ipv4/arp.c
>     <http://elixir.free-electrons.com/linux/latest/source/net/ipv4/arp.c>____
>
>     __ __
>
>     static int arp_ignore
>     <http://elixir.free-electrons.com/linux/latest/ident/arp_ignore>(struct
>     in_device
>     <http://elixir.free-electrons.com/linux/latest/ident/in_device>
>     *in_dev, __be32
>     <http://elixir.free-electrons.com/linux/latest/ident/__be32> sip
>     <http://elixir.free-electrons.com/linux/latest/ident/sip>, __be32
>     <http://elixir.free-electrons.com/linux/latest/ident/__be32> tip)____
>
>     {____
>
>                         struct net *net = dev_net
>     <http://elixir.free-electrons.com/linux/latest/ident/dev_net>(in_dev->dev);____
>
>                         int scope
>     <http://elixir.free-electrons.com/linux/latest/ident/scope>;____
>
>     __ __
>
>                         switch (IN_DEV_ARP_IGNORE
>     <http://elixir.free-electrons.com/linux/latest/ident/IN_DEV_ARP_IGNORE>(in_dev))
>     {____
>
>                         case 0:          /* Reply, the tip is already
>     validated */____
>
>                                              return 0;____
>
>                         case 1:          /* Reply only if tip is
>     configured on the incoming interface */____
>
>                                              sip
>     <http://elixir.free-electrons.com/linux/latest/ident/sip> = 0;____
>
>                                              scope
>     <http://elixir.free-electrons.com/linux/latest/ident/scope> =
>     RT_SCOPE_HOST
>     <http://elixir.free-electrons.com/linux/latest/ident/RT_SCOPE_HOST>;____
>
>                                              break;____
>
>                         case 2:          /*____
>
>                                              * Reply only if tip is
>     configured on the incoming interface____
>
>                                              * and is in same subnet as
>     sip____
>
>                                              */____
>
>                                              scope
>     <http://elixir.free-electrons.com/linux/latest/ident/scope> =
>     RT_SCOPE_HOST
>     <http://elixir.free-electrons.com/linux/latest/ident/RT_SCOPE_HOST>;____
>
>                                              break;____
>
>     I have two linux boxes with ubuntu 16.04 connected on an ethernet ____
>
>     and with two different subnet:____
>
>     lenovo (enp3s0 with IP 192.168.1.35/24<http://192.168.1.35/24> <http://192.168.1.35/24>) <—>
>     vaio (enp2s8 with IP 192.168.2.100/24<http://192.168.2.100/24> <http://192.168.2.100/24>)____
>
>     __ __
>
>     on vaio: I run an arping to request ARP resolution of 192.168.1.35
>     <http://192.168.1.35>:____
>
>     vaio:~$ sudo arping 192.168.1.35 -i enp2s8____
>
>     60 bytes from ec:a8:6b:c0:82:23 (192.168.1.35): index=0 time=6.538
>     msec____
>
>     60 bytes from ec:a8:6b:c0:82:23 (192.168.1.35): index=1 time=1.464
>     msec____
>
>     60 bytes from ec:a8:6b:c0:82:23 (192.168.1.35): index=2 time=8.418
>     msec____
>
>     __ __
>
>     I made sure on lenovo as described arp_announce is ‘2’, and
>     arp_ignore is ‘0’:____
>
>     root@lenovo:/proc/sys/net/ipv4/conf/enp3s0# echo 2 > arp_announce ____
>
>     root@lenovo:/proc/sys/net/ipv4/conf/enp3s0# cat arp_ignore ____
>
>     __ __
>
>     Run tcpdump on lenovo interface enp3s0 to get ARP packets:____
>
>     root@lenovo:/proc/sys/net/ipv4/conf/enp3s0# tcpdump -i enp3s0 arp
>     -vv____
>
>     __ __
>
>     22:14:01.774491 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
>     192.168.1.35 tell 192.168.2.100, length 46____
>
>     22:14:01.774511 ARP, Ethernet (len 6), IPv4 (len 4), Reply
>     192.168.1.35 is-at ec:a8:6b:c0:82:23 (oui Unknown), length 28____
>
>     22:14:02.775522 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
>     192.168.1.35 tell 192.168.2.100, length 46____
>
>     22:14:02.775541 ARP, Ethernet (len 6), IPv4 (len 4), Reply
>     192.168.1.35 is-at ec:a8:6b:c0:82:23 (oui Unknown), length 28____
>
>     __ __
>
>     __ __
>
>     Ok, so what I’m getting at is that, if you know the system needs to
>     run____
>
>     numbered and mismatched IP addresses over the same cable, then____
>
>     regardless of p2p-over-lan or other applications, you probably need
>     to____
>
>     adjust the local ARP behavior to match what is expected on the OS.____
>
>     __ __
>
>     I agree that RFC 5309 does mention the matching IP subnet, and
>     probably____
>
>     should refer to unnumbered is the most useful use case.____
>
>     __ __
>
>     Best Regards,____
>
>     - Naiming____
>
>     __ __
>
>         On May 1, 2017, at 12:40 AM, Alexander Vainshtein
>         <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
>         <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>> wrote:____
>
>         __ __
>
>         Naiming,____
>
>         Lots of thanks for a prompt response.____
>
>          ____
>
>         Unfortunately, I do not think that your response addresses your
>         concern.____
>
>          ____
>
>         RFC 5309 explicitly mentions “ARP implementation (which /checks
>         that the subnet of the source address of the ARP request matches
>         the local interface address/)”. Actually, ARP implementations
>         frequently check that /the source IP address in an ARP request
>         is in the subnet of the local interface address/. E.g., AFAIK,
>         this is the standard behavior of the Linux ARP implementation.
>         To the best of my understanding this was the check that RFC 5309
>         implied, /because there is no way the subnet of the source
>         address of the ARP request could be known/.____
>
>          ____
>
>         If such check is applied, then the scenario I’ve described
>         becomes valid. I can add that I have observed several
>         implementations that experience the described behavior (i.e.,
>         blackholing of unicast IP traffic that OSPF tries to route via
>         such a link). Some other implementations seem to behave better.____
>
>          ____
>
>         Regards,____
>
>         Sasha____
>
>          ____
>
>          ____
>
>          ____
>
>          ____
>
>          ____
>
>         Regards,____
>
>         Sasha____
>
>          ____
>
>         Office: +972-39266302<tel:%2B972-39266302> <tel:+972%203-926-6302>____
>
>         Cell:      +972-549266302<tel:%2B972-549266302> <tel:+972%2054-926-6302>____
>
>         Email:   Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
>         <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>____
>
>          ____
>
>         *From:* Naiming Shen (naiming) [mailto:naiming@cisco.com<mailto:naiming@cisco.com>]
>         *Sent:* Monday, May 01, 2017 5:34 AM
>         *To:* Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
>         <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>>
>         *Cc:* Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>
>         <mailto:ginsberg@cisco.com<mailto:ginsberg@cisco.com>>>; isis-wg@ietf.org<mailto:isis-wg@ietf.org>
>         <mailto:isis-wg@ietf.org<mailto:isis-wg@ietf.org>>; RFC Errata System
>         <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org> <mailto:rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>>;
>         alex.zinin@alcatel-lucent.com<mailto:alex.zinin@alcatel-lucent.com>
>         <mailto:alex.zinin@alcatel-lucent.com<mailto:alex.zinin@alcatel-lucent.com>>; akatlas@gmail.com<mailto:akatlas@gmail.com>
>         <mailto:akatlas@gmail.com<mailto:akatlas@gmail.com>>; db3546@att.com<mailto:db3546@att.com>
>         <mailto:db3546@att.com<mailto:db3546@att.com>>; Alvaro Retana (aretana)
>         <aretana@cisco.com<mailto:aretana@cisco.com> <mailto:aretana@cisco.com<mailto:aretana@cisco.com>>>;
>         chopps@chopps.org<mailto:chopps@chopps.org> <mailto:chopps@chopps.org<mailto:chopps@chopps.org>>; hannes@gredler.at<mailto:hannes@gredler.at>
>         <mailto:hannes@gredler.at<mailto:hannes@gredler.at>>
>         *Subject:* Re: [Isis-wg] [Technical Errata Reported] RFC5309
>         (5007)____
>
>          ____
>
>          ____
>
>         Alexander, ____
>
>          ____
>
>         If you are saying the local LAN interface is explicitly
>         configured with____
>
>         a different subnet IP address then the peer, I don’t think there
>         is any____
>
>         problem with the ARP, and also with this RFC. Since ARP will
>         always____
>
>         reply to answer its own IP addresses on the interface upon
>         request.____
>
>          ____
>
>         This RFC is only saying, if it’s p2p-over-lan over an unnumbered
>         IP address,____
>
>         and this LAN interface needs to proxy-ARP the IP address it
>         binds to.____
>
>         If the ARP already replies since you have an IP address, and our____
>
>         p2p-over-LAN intf also uses this IP address, nothing is broken.____
>
>          ____
>
>         thanks.____
>
>         - Naiming____
>
>          ____
>
>             On Apr 30, 2017, at 8:50 AM, Alexander Vainshtein
>             <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
>             <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>> wrote:____
>
>              ____
>
>             Les,____
>
>             Lots of thanks for a prompt response.____
>
>              ____
>
>             As I see it, the difference between the P2P and LAN modes is
>             essential for OSPF:____
>
>             - If an OSPF interface is a LAN (broadcast) interface, there
>             is a check of the same subnet for received Hello packets. If
>             the received Hello packets do not pass this check, they are
>             discarded and an error is reported via SNMP.____
>
>             - However, if an OSPF interface is a P2P interface, then the
>             subnet check on the Hello packets is bypassed  by design as
>             defined in Section 10.5 of RFC 2328:____
>
>                    ____
>
>                                  The generic input processing of OSPF
>             packets will____
>
>                     have checked the validity of the IP header and the
>             OSPF packet____
>
>                     header.  Next, the values of the Network Mask,
>             HelloInterval,____
>
>                     and RouterDeadInterval fields in the received Hello
>             packet must____
>
>                     be checked against the values configured for the
>             receiving____
>
>                     interface.  Any mismatch causes processing to stop
>             and the____
>
>                     packet to be dropped.  In other words, the above
>             fields are____
>
>                     really describing the attached network's
>             configuration. However,____
>
>                     there is one exception to the above rule: on
>             point-to-point____
>
>                     networks and on virtual links, the Network Mask in
>             the received____
>
>                     Hello Packet should be ignored.____
>
>              ____
>
>             I.e., having different subnets on two ends of a PPP link
>             would not cause any problems for OSPF - the adjacency would
>             be successfully recognized, it would progress to its FULL
>             state, and unicast traffic would cross such a link without
>             any problem.____
>
>              ____
>
>             But if we have a P2P-over-LAN link (which is the case for
>             RFC 5309), the result would be quite different - unless the
>             ARP implementations go beyond what 5309 says and relax the
>             check for all such links, be they numbered or unnumbered.____
>
>              ____
>
>             Do I miss something substantial here?____
>
>              ____
>
>              ____
>
>              ____
>
>             Regards,____
>
>             Sasha____
>
>              ____
>
>             Office: +972-39266302<tel:%2B972-39266302> <tel:+972%203-926-6302>____
>
>             Cell:      +972-549266302<tel:%2B972-549266302> <tel:+972%2054-926-6302>____
>
>             Email:   Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
>             <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>____
>
>              ____
>
>              ____
>
>             -----Original Message-----
>             From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com<mailto:ginsberg@cisco.com>]
>             Sent: Sunday, April 30, 2017 5:19 PM
>             To: RFC Errata System <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>
>             <mailto:rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>>; Naiming Shen (naiming)
>             <naiming@cisco.com<mailto:naiming@cisco.com>
>             <mailto:naiming@cisco.com<mailto:naiming@cisco.com>>>;alex.zinin@alcatel-lucent.com<mailto:alex.zinin@alcatel-lucent.com>
>             <mailto:alex.zinin@alcatel-lucent.com<mailto:alex.zinin@alcatel-lucent.com>>; akatlas@gmail.com<mailto:akatlas@gmail.com>
>             <mailto:akatlas@gmail.com<mailto:akatlas@gmail.com>>; db3546@att.com<mailto:db3546@att.com>
>             <mailto:db3546@att.com<mailto:db3546@att.com>>; Alvaro Retana (aretana)
>             <aretana@cisco.com<mailto:aretana@cisco.com>
>             <mailto:aretana@cisco.com<mailto:aretana@cisco.com>>>; chopps@chopps.org<mailto:chopps@chopps.org>
>             <mailto:chopps@chopps.org<mailto:chopps@chopps.org>>; hannes@gredler.at<mailto:hannes@gredler.at>
>             <mailto:hannes@gredler.at<mailto:hannes@gredler.at>>
>             Cc: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
>             <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>>; isis-wg@ietf.org<mailto:isis-wg@ietf.org>
>             <mailto:isis-wg@ietf.org<mailto:isis-wg@ietf.org>>
>             Subject: RE: [Isis-wg] [Technical Errata Reported] RFC5309
>             (5007)____
>
>              ____
>
>             Alexander -____
>
>              ____
>
>             I am not speaking for the RFC authors, but regarding your
>             point:____
>
>              ____
>
>             > o          Are assigned with IP addresses and subnet masks yielding different____
>
>             > subnets____
>
>              ____
>
>             I fail to see why this issue is unique to (or associated
>             with) running in P2P mode.____
>
>              ____
>
>             The unnumbered case is specifically mentioned because in
>             such a case it can be expected that the next hop address
>             will be a loopback address and therefore there will be no
>             common subnet.____
>
>             But in the numbered case whether you have one neighbor in
>             P2P mode or many neighbors in multi-access mode the
>             msimatched subnet issue is the same. Therefore I see no
>             reason why these RFCs should discuss it.____
>
>              ____
>
>             ???____
>
>              ____
>
>                Les____
>
>              ____
>
>              ____
>
>             > -----Original Message-----____
>
>             > From: Isis-wg [mailto:isis-wg-bounces@ietf.org<mailto:isis-wg-bounces@ietf.org>
>             <mailto:isis-wg-bounces@ietf.org<mailto:isis-wg-bounces@ietf.org>>] On Behalf Of RFC____
>
>             > Errata System____
>
>             > Sent: Sunday, April 30, 2017 1:16 AM____
>
>             > To: Naiming Shen (naiming); alex.zinin@alcatel-lucent.com<mailto:alex.zinin@alcatel-lucent.com>
>             <mailto:alex.zinin@alcatel-lucent.com<mailto:alex.zinin@alcatel-lucent.com>>;____
>
>             > akatlas@gmail.com<mailto:akatlas@gmail.com>
>             <mailto:akatlas@gmail.com<mailto:akatlas@gmail.com>>; db3546@att.com<mailto:db3546@att.com>
>             <mailto:db3546@att.com<mailto:db3546@att.com>>; Alvaro Retana (aretana);____
>
>             > chopps@chopps.org<mailto:chopps@chopps.org>
>             <mailto:chopps@chopps.org<mailto:chopps@chopps.org>>; hannes@gredler.at<mailto:hannes@gredler.at>
>             <mailto:hannes@gredler.at<mailto:hannes@gredler.at>>____
>
>             > Cc: Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
>             <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>; isis-wg@ietf.org<mailto:isis-wg@ietf.org>
>             <mailto:isis-wg@ietf.org<mailto:isis-wg@ietf.org>>;____
>
>             > rfc-editor@rfc- editor.org<http://webdefence.global.blackspider.com/urlwrap/?q=AXicE3RmiL7GwDDlCANDUU6lgWGSXnFRmV5uYmZOcn5eSVF-jl5yfi5DmamrR0pRaaaBsaW5hQGDY05qRWJeSmqRXlhiZl5xRklqZp5DanJmSWpOKlh9RklJgZW-fmpKZkl-kV5-UToDA0PFQQYGAP3EJNg&Z>
>             <http://webdefence.global.blackspider.com/urlwrap/?q=AXicE3RmiL7GwDDlCANDUU6lgUmSXnFRmV5uYmZOcn5eSVF-jl5yfi5DmYmhUUREcLmBkaGRuQmDY05qRWJeSmqRXlhiZl5xRklqZp5DanJmSWpOKlh9RklJgZW-fmpKZkl-kV5-UToDA0PFQQYGAOFQJGs&Z>____
>
>             > Subject: [Isis-wg] [Technical Errata Reported] RFC5309 (5007)____
>
>             > ____
>
>             > The following errata report has been submitted for RFC5309,____
>
>             > "Point-to-Point Operation over LAN in Link State Routing Protocols".____
>
>             > ____
>
>             > --------------------------------------____
>
>             > You may review the report below and at:____
>
>             > http://www.rfc-editor.org/errata_search.php?rfc=5309&eid=5007
>             <http://www.rfc-editor.org/errata_search.php?rfc=5309&eid=5007>____
>
>             > ____
>
>             > --------------------------------------____
>
>             > Type: Technical____
>
>             > Reported by: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>
>             <mailto:Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>>____
>
>             > ____
>
>             > Section: 4.3____
>
>             > ____
>
>             > Original Text____
>
>             > -------------____
>
>             > For the ARP implementation (which checks that the subnet of the source____
>
>             > address of the ARP request matches the local interface address), this____
>
>             > check needs to be relaxed for the unnumbered p2p-over-lan circuits.____
>
>             > ____
>
>             > Corrected Text____
>
>             > --------------____
>
>             > For the ARP implementation (which checks that the subnet of the source____
>
>             > address of the ARP request matches the local interface address), this____
>
>             > check needs to be relaxed for the p2p-over-lan circuits (both numbered____
>
>             > and unnumbered).____
>
>             > ____
>
>             > Notes____
>
>             > -----____
>
>             > Consider the following situation:____
>
>             > 1.         Two routers, R1 and R2, are connected by a physical P2P  Ethernet____
>
>             > link____
>
>             > 2.         OSPFv2 is enabled on the interfaces representing the endpoints of____
>
>             > this link.____
>
>             > 3.      From the OSPF POV these interfaces:____
>
>             > o          Are configured as P2P____
>
>             > o          Belong to the same area____
>
>             > o          Are assigned with IP addresses and subnet masks yielding different____
>
>             > subnets____
>
>             > 4.    ARP check mentioned in the problematic text is not relaxed.____
>
>             > ____
>
>             > Under this conditions:____
>
>             > -Both R1 and R2 will accept Hello messages sent by the other router____
>
>             > (becase it ignores subnet in Hello messages received via P2P____
>
>             > interfaces)____
>
>             > - Adjacency between R1 and R2 will progress to FULL state (because all____
>
>             > OSPFv2 messages will be sent with AllSPFRouters multicast IPv4____
>
>             > address)____
>
>             > - Unicast traffic sent by R1 to R2 (and vice versa) will be blackholed____
>
>             > because ARP will not resolve addresses assigned to the corresponding interfaces.____
>
>             > ____
>
>             > Instructions:____
>
>             > -------------____
>
>             > This erratum is currently posted as "Reported". If necessary, please____
>
>             > use "Reply All" to discuss whether it should be verified or rejected.____
>
>             > When a decision is reached, the verifying party can log in to change____
>
>             > the status and edit the report, if necessary.____
>
>             > ____
>
>             > --------------------------------------____
>
>             > RFC5309 (draft-ietf-isis-igp-p2p-over-lan-06)____
>
>             > --------------------------------------____
>
>             > Title               : Point-to-Point Operation over LAN in Link State Routing____
>
>             > Protocols____
>
>             > Publication Date    : October 2008____
>
>             > Author(s)           : N. Shen, Ed., A. Zinin, Ed.____
>
>             > Category            : INFORMATIONAL____
>
>             > Source              : IS-IS for IP Internets____
>
>             > Area                : Routing____
>
>             > Stream              : IETF____
>
>             > Verifying Party     : IESG____
>
>             > ____
>
>             > ___________________________________________________
>
>             > Isis-wg mailing list____
>
>             > Isis-wg@ietf.org<mailto:Isis-wg@ietf.org> <mailto:Isis-wg@ietf.org<mailto:Isis-wg@ietf.org>>____
>
>             > https://www.ietf.org/mailman/listinfo/isis-wg
>             <https://www.ietf.org/mailman/listinfo/isis-wg>____
>
>
>             ___________________________________________________________________________
>
>             This e-mail message is intended for the recipient only and
>             contains information which is
>             CONFIDENTIAL and which may be proprietary to ECI Telecom. If
>             you have received this
>             transmission in error, please inform us by e-mail, phone or
>             fax, and then delete the original
>             and all copies thereof.
>             _______________________________________________________________________________
>
>          ____
>
>
>         ___________________________________________________________________________
>
>         This e-mail message is intended for the recipient only and
>         contains information which is
>         CONFIDENTIAL and which may be proprietary to ECI Telecom. If you
>         have received this
>         transmission in error, please inform us by e-mail, phone or fax,
>         and then delete the original
>         and all copies thereof.
>         _______________________________________________________________________________
>
>     __ __
>
>
>     ___________________________________________________________________________
>
>     This e-mail message is intended for the recipient only and contains
>     information which is
>     CONFIDENTIAL and which may be proprietary to ECI Telecom. If you
>     have received this
>     transmission in error, please inform us by e-mail, phone or fax, and
>     then delete the original
>     and all copies thereof.
>     ___________________________________________________________________________
>
>



___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is 
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this 
transmission in error, please inform us by e-mail, phone or fax, and then delete the original 
and all copies thereof.
___________________________________________________________________________