Re: [ippm] Vote at IPPM session

"MORTON, ALFRED C (AL)" <acmorton@att.com> Wed, 19 April 2017 20:02 UTC

Return-Path: <acmorton@att.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E12128D40; Wed, 19 Apr 2017 13:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.9
X-Spam-Level:
X-Spam-Status: No, score=-4.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 B9lXqlf83zAE; Wed, 19 Apr 2017 13:02:57 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 5C7E212894A; Wed, 19 Apr 2017 13:02:57 -0700 (PDT)
Received: from pps.filterd (m0083689.ppops.net [127.0.0.1]) by m0083689.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v3JJt4lj029849; Wed, 19 Apr 2017 16:02:54 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0083689.ppops.net-00191d01. with ESMTP id 29xe0bh8t4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Apr 2017 16:02:54 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3JK2qUG012209; Wed, 19 Apr 2017 16:02:53 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3JK2gJ4012038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 19 Apr 2017 16:02:47 -0400
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Wed, 19 Apr 2017 20:02:31 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v3JK2VFA004977; Wed, 19 Apr 2017 15:02:31 -0500
Received: from mail-azure.research.att.com (mail-azure.research.att.com [135.207.255.18]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v3JK2NkC004626; Wed, 19 Apr 2017 15:02:23 -0500
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-azure.research.att.com (Postfix) with ESMTP id A8647E08B9; Wed, 19 Apr 2017 16:02:22 -0400 (EDT)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0319.002; Wed, 19 Apr 2017 16:02:22 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
CC: "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, "ietf@trammell.ch" <ietf@trammell.ch>, "fbrockne@cisco.com" <fbrockne@cisco.com>
Thread-Topic: [ippm] Vote at IPPM session
Thread-Index: AQHSp+ANywb7w7Y7CUWYR5PjBqbNA6GqudOAgAAD3QCAAAfSAIAAIx6AgAA2hgCAAPdoAIAAaFWAgAAcNwD//8lsgIAC5LeAgAt5d4CABF/eAIADEXMAgARQ+4CABTbyAIAAKoCA///CZvCAAQO0gIAAkNsg
Date: Wed, 19 Apr 2017 20:02:21 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF25F72473@njmtexg5.research.att.com>
References: <CA+RyBmXAyOVZy2DncvC9Bdkmt2P+OXhV49sFgCqXf=1Of3EWkw@mail.gmail.com> <830D269B-62A1-4782-8AFE-C2910F908BFF@trammell.ch> <CA+RyBmUtVv6fJVLrUxwLiHg9ktvDCkuV0s+KWyv4ygEb50rMOw@mail.gmail.com> <01fa01d2a7e9$1c65d520$55317f60$@olddog.co.uk> <8168bd84-88f4-c40b-7150-844b463f6612@trammell.ch> <CAKKJt-ca7VgePkstLE=RLTh506o44m3hiZ_ay88hOS1egz20KA@mail.gmail.com> <7e592d5c42d44db594dfdfbc76233e29@XCH-RCD-008.cisco.com> <3E70CF9A-5A09-419B-B330-F9B854E01539@trammell.ch> <01c801d2a8d3$eb6d2450$c2476cf0$@olddog.co.uk> <4D7F4AD313D3FC43A053B309F97543CF25F3D4C0@njmtexg5.research.att.com> <e60a1ae521054eb3b9e1352d5918c6b2@XCH-RCD-008.cisco.com> <2BCD950B-DEBF-4FCD-92DD-89BE50270006@encrypted.net> <aa0dea09d3e44260a2ed306836c68ccb@XCH-RCD-008.cisco.com> <45679B2A-EE96-4980-BAED-B39994C73CFE@encrypted.net> <070501d2b5c8$dc264d30$9472e790$@olddog.co.uk> <58b68d6d47614281846807b6353b46f3@XCH-RCD-008.cisco.com> <38C60635-D7B8-4AA9-843D-ABBA65AC3D62@trammell.ch> <4D7F4AD313D3FC43A053B309F97543CF25F71AE7@njmtexg5.research.att.com> <17864478fa3b4b58894f8b3c701505f4@HE101653.emea1.cds.t-internal.com>
In-Reply-To: <17864478fa3b4b58894f8b3c701505f4@HE101653.emea1.cds.t-internal.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.249.244]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-19_16:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704190165
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/-wyMOM8opcD3gUC-ORLxA5R036o>
Subject: Re: [ippm] Vote at IPPM session
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 20:02:59 -0000

Hi RĂ¼diger,
short reply in-line,
Al

> -----Original Message-----
> From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]
> Sent: Wednesday, April 19, 2017 3:15 AM
> To: MORTON, ALFRED C (AL)
> Cc: ippm-chairs@ietf.org; ippm@ietf.org; ietf@trammell.ch;
> fbrockne@cisco.com
> Subject: AW: [ippm] Vote at IPPM session
> 
> Hi Al,
> 
> is a non-iOAM network operator able to detect standard ipv6 packets with
> iOAM extensions, if the receiving operators equipment is configured to
> support standard ipv6 protocol only? The pre-condition here is "non-iOAM
> domain" at the receiving side. My point is, if a domain isn't interested
> in supporting the iOAM extensions, is it obliged to operate iOAM aware
> equipment to detect undesired traffic at network boundaries?
[ACM] 
No, an operator can let the traffic flow if they want.
However, if operators find that their network is 
affected by traffic with iOAM data from another domain,
they would be justified to discard that traffic
(as long as there is a clear domain limit expressed to 
iOAM protocol designers of the future, as Frank has
suggested).

This is the same ability afforded operators by declaring
BMWG address space for isolated testing-only, or the
various private network address spaces. Plenty of 
Net10 traffic escapes, and operators are not obliged
to drop it, but they certainly can.

> 
> I'm not sure, whether this is an IPPM discussion. Is there any other
> IPPM protocol or packet content requiring a discard of traffic at a
> domain boundary?
> 
> Regards,
> 
> Ruediger
> 
> 
>  [ACM]
> 
> IOM, there is a general message to convey for all future protocol
> development. Something like "sufficient provisions should be made to
> restrict the iOAM traffic to the intended domain."
> 
> We could provide guidance to interconnecting network operators, as well,
> effectively allowing them to discard traffic containing unexpected iOAM
> data. This would be applicable to non-iOAM network operators, but might
> be more important for interconnecting operators who have established
> their own iOAM domain.
> 
> This is similar to the approach we used for BMWG test traffic:
> there are v4 and v6 address spaces dedicated for isolated test
> environments, and any packet with testing addresses observed on the
> Internet may be discarded.
>