Re: [manet] DLEP IP addr conflicting add/drop

"Ratliff, Stanley" <sratliff@idirect.net> Thu, 20 October 2016 15:01 UTC

Return-Path: <sratliff@idirect.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9E921294A6 for <manet@ietfa.amsl.com>; Thu, 20 Oct 2016 08:01:13 -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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=idirect.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 5OAkrQeULaxi for <manet@ietfa.amsl.com>; Thu, 20 Oct 2016 08:01:06 -0700 (PDT)
Received: from mx0b-00229401.pphosted.com (mx0a-00229401.pphosted.com [148.163.157.249]) (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 D5FCC129644 for <manet@ietf.org>; Thu, 20 Oct 2016 08:01:06 -0700 (PDT)
Received: from pps.filterd (m0097894.ppops.net [127.0.0.1]) by mx0b-00229401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u9KEurU2023744; Thu, 20 Oct 2016 11:01:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=idirect.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=dk1; bh=58NjgyAyR4+aMyrmY4pIB/78dzBPeQFFetYBOM+WyBo=; b=dDA4u9qZP4YFQaVI3v8dQokjjkTrye4ste48rQocV6jyiiQETRcwN7RaYwswLzR/mxSM sBhXleQn3jFDEIVVqId+QvYEvN+BW3NES1lVqFng3cDdNaGbdgQsB+urxiWSHDm0Z5wn Q46FvxKRNspb42aj4NirvUPNlTh/yy/BIOoIovUmrKAn8cxxLnX9POuRZn6muHM3jnTY HUPiKTPqf+7XKuIxhTht2uhkWsL6W3Ps1s1YsWn0CmILcSdIG0C/OCpZfJ1evYo1uuvM qt62NZOVq8rbL2WYihX/4gO3qVKfxXEenbMBStpvUcQxDjSwIlo93SAMAcZIai20vQPs lA==
Received: from webmail.idirect.net ([198.180.159.2]) by mx0b-00229401.pphosted.com with ESMTP id 263g80bdpj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 20 Oct 2016 11:01:05 -0400
Received: from VAUSDITCHM2.idirect.net (10.250.250.202) by VAUSDITCHM3.idirect.net (10.250.250.203) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Oct 2016 11:01:03 -0400
Received: from VAUSDITCHM2.idirect.net ([fe80::b5b6:9e50:3403:e75d]) by VAUSDITCHM2.idirect.net ([fe80::b5b6:9e50:3403:e75d%15]) with mapi id 15.00.1210.000; Thu, 20 Oct 2016 11:01:03 -0400
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>, "manet@ietf.org" <manet@ietf.org>
Thread-Topic: DLEP IP addr conflicting add/drop
Thread-Index: AQHSKt9NGA5PXwBDm0+fM2tXgnkt6KCxbuCA
Date: Thu, 20 Oct 2016 15:01:02 +0000
Message-ID: <3292b0e7eb8d409d8f511af284c171e0@VAUSDITCHM2.idirect.net>
References: <D42E4E9A.3491%David.Wiggins@ll.mit.edu>
In-Reply-To: <D42E4E9A.3491%David.Wiggins@ll.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.250.250.20]
Content-Type: multipart/alternative; boundary="_000_3292b0e7eb8d409d8f511af284c171e0VAUSDITCHM2idirectnet_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-10-20_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outboundspam_notspam policy=outboundspam score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1610200269
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/-LfEGroDjFuR1wP0n7mJ_P8_mZw>
Subject: Re: [manet] DLEP IP addr conflicting add/drop
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2016 15:01:14 -0000

David,

The current thinking amongst the editing team is that these types of "logical inconsistencies" will, indeed, result in an error - the message should be acknowledged, but with a Status Data Item indicating the error. We've gone around and around as to whether the error should be fatal or not (e.g. is the mode "Terminate" or "Continue"). Our thinking is that the mode should be "Continue".

Any other opinions on that?

Regards,
Stan


From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Wiggins, David - 0665 - MITLL
Sent: Thursday, October 20, 2016 10:36 AM
To: manet@ietf.org
Subject: [manet] DLEP IP addr conflicting add/drop

What should happen if a DLEP message contains an IPv4/6 Address or Attached Subnet data item with Flags=Add, and also contains another data item with the *same* IP address/subnet, but with Flags=Drop?  I don't think the handling in this case specified.

I think this condition should result in a DLEP error, since it indicates that the sender is quite confused.

This is similar to my message to the list on August 4, but this is a different case.

David

============================================================================================================================================
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.