IETF Logo Mail Archive

Re: [manet] Stephen Farrell's No Objection on draft-ietf-manet-rfc6779bis-06: (with COMMENT)

"Alvaro Retana (aretana)" <aretana@cisco.com> Wed, 01 June 2016 19:04 UTC

Return-Path: <aretana@cisco.com>
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 3D33F12D169; Wed, 1 Jun 2016 12:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level:
X-Spam-Status: No, score=-15.947 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 Nn5w12doi7nX; Wed, 1 Jun 2016 12:04:16 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56C2112D105; Wed, 1 Jun 2016 12:04:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1742; q=dns/txt; s=iport; t=1464807856; x=1466017456; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=sqXmVPHPaTwJe480RXbfWM9Z0wKP1EKqEf2BZ2VqQYE=; b=RcSiDr0X4b0zbKEpJjoExwRYZZEORcxo7qLt6f04ZT1shEJguhVTdUcO R+Hu3S+zJKFgYlK72H1/nabZuZbDbaGI1W9q6EmcUYRUy29CuItSzg7NQ tPm+Gj1ilLBFHpmVCzOWHjOSosRicDyh6IQCw3E2iwMYvAs07z8Ygcro3 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AUAgC/ME9X/4ENJK1dgz1WfQa4B4IPAQ2BeiKFbwKBMzgUAQEBAQEBAWUnhEYBAQQ6PxACAQg2EDIlAgQBDQWILw7BRQEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhieETYoaAQSTN4UAAYV/iCCBaY0zhjOJGAEeAQFCgjiBNW4BiTd/AQEB
X-IronPort-AV: E=Sophos;i="5.26,402,1459814400"; d="scan'208";a="108752418"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Jun 2016 19:04:15 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u51J4F65012612 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 1 Jun 2016 19:04:15 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 1 Jun 2016 14:04:14 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1104.009; Wed, 1 Jun 2016 14:04:14 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
Thread-Topic: Stephen Farrell's No Objection on draft-ietf-manet-rfc6779bis-06: (with COMMENT)
Thread-Index: AQHRvDJ9CFMjRTaJCkyR1x/XY1vj8J/VCSGA
Date: Wed, 01 Jun 2016 19:04:14 +0000
Message-ID: <D374A7B9.12A3A1%aretana@cisco.com>
References: <20160601182154.16139.60497.idtracker@ietfa.amsl.com>
In-Reply-To: <20160601182154.16139.60497.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.2.160219
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8F54062C465471488F8C94FC70F95512@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/xyLIq5erfsRctmzlA3cfLj9YFlI>
Cc: "chris.dearlove@baesystems.com" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-rfc6779bis@ietf.org" <draft-ietf-manet-rfc6779bis@ietf.org>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>
Subject: Re: [manet] Stephen Farrell's No Objection on draft-ietf-manet-rfc6779bis-06: (with COMMENT)
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: Wed, 01 Jun 2016 19:04:18 -0000

On 6/1/16, 2:21 PM, "iesg on behalf of Stephen Farrell"
<iesg-bounces@ietf.org on behalf of
stephen.farrell@cs.tcd.ie> wrote:

Stephen:

Hi!

>- The security considerations section doesn't seem to
>reflect the latest boilerplate. [2] Should it? I'm not
>making this a discuss as it's a minor change to a MIB and
>I accept that it's arguable that folks might not update
>their SNMP security code whilst doing this. But I don't
>think I've seen this case before (minor update to MIB
>without changed security boilerplate) so maybe the IESG
>should chat about it to decide if there's anything to be
>done here.

The variations from the boilerplate are minimal:

Boilerplate>
   ...The support for SET operations in a non-secure
   environment without proper protection opens devices to attack.

...
   Implementations SHOULD provide the security features described by the
   SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance 
   to the SNMPv3 standard MUST include full support for authentication and
   privacy via the User-based Security Model (USM) [RFC3414] with the AES
   cipher algorithm [RFC3826].



rfc6779bis>
   ...The support for SET operations in a non-secure
   environment without proper protection can have a negative effect on
   network operations.

...
   Implementations MUST provide the security features described by the
   SNMPv3 framework (see [RFC3410]), including full support for
   authentication and privacy via the User-based Security Model (USM)
   [RFC3414] with the AES cipher algorithm [RFC3826].


I don't have any issues with making the text match.

Alvaro.



>   [2] https://trac.tools.ietf.org/area/ops/trac/wiki/mib-security

v2.23.0 | Report a Bug | By Email