Re: [v6ops] [saag] ITU-T SG17 IPv6 security work items liaison

Bob Hinden <bob.hinden@gmail.com> Tue, 14 June 2011 04:51 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39B9B11E8132; Mon, 13 Jun 2011 21:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level:
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_RECV_BEZEQINT_B=0.763, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pA8WQ1nMPHJp; Mon, 13 Jun 2011 21:51:53 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id D38A411E80BE; Mon, 13 Jun 2011 21:51:52 -0700 (PDT)
Received: by wwk4 with SMTP id 4so3173310wwk.1 for <multiple recipients>; Mon, 13 Jun 2011 21:51:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=6AThwAjNBVwPIKrUgpuFEpb/oXzGgDCcnmzweIpCl+Y=; b=NV3Qq92MVq0LJRz9+0UOFrFG20XgQ1OlawVA9896fKvBJ+SGYB1MPl6A9UZpQz+bhf GYbHxuoQe1pmqKTfhfA1Z4VTrXsKO8UKpgUWkhweRYrkNSEMJTUHIefMK5Abbvyh9S6u CziJVwgJMkI+N1l8fWDTRmbG/zWlu/5JzJQwc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=Kxho02N5kcfl28ZqEuMuPQJMjWGd5N7avksGSVy2VcIOyY0xTg7CFcujz7xHAVW67t j1Q5pqte8yl0jfy59w/po6+CXHVLLKatULLejgrzARwH9zXCDRQ0h/bAdHbw0bGiPkpo RWCteZJatH0jaxGP1FVvonGDmidwVujGB3TSc=
Received: by 10.227.196.193 with SMTP id eh1mr5937739wbb.12.1308027098894; Mon, 13 Jun 2011 21:51:38 -0700 (PDT)
Received: from [192.168.4.127] (bzq-218-39-93.cablep.bezeqint.net [81.218.39.93]) by mx.google.com with ESMTPS id fl19sm4717598wbb.49.2011.06.13.21.51.37 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 13 Jun 2011 21:51:38 -0700 (PDT)
Subject: Re: [v6ops] [saag] ITU-T SG17 IPv6 security work items liaison
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="windows-1252"
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <D4359E14-EFD7-4780-9EB1-02F4AFF9A35D@vigilsec.com>
Date: Tue, 14 Jun 2011 07:51:35 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <22C01597-E89D-4200-8251-2F3979ABB0B6@gmail.com>
References: <4DEA6323.4070302@cs.tcd.ie> <4DF69899.2050606@cs.tcd.ie> <D4359E14-EFD7-4780-9EB1-02F4AFF9A35D@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1084)
Cc: ipv6@ietf.org, v6ops@ietf.org, Bob Hinden <bob.hinden@gmail.com>, "saag@ietf.org" <saag@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 04:51:54 -0000

Russ,

On Jun 14, 2011, at 2:57 AM, Russ Housley wrote:

> Stephen:
> 
> Comments below.
> 
> Russ
> 
> 
>> From:  IETF Security Area
>> To: Study Group 17, Questions 2 and 3
>> Title: Work on Security of IPv6
>> 
>> FOR ACTION
>> 
>> The IETF thanks Study Group 17 for its liaison LS-206 "Liaison on IPv6
>> security issues".  As the world transitions to IPv6, new opportunities
>> and challenges and challenges arise.  SG17's new focus on deployment and
> 
> s/and challenges and challenges/and challenges/
> s/new//
> 
>> implementation considerations reflects this reality.   We would like to
>> bring to your attention the following work which we believe may prove a
>> useful basis for both X.ipv6-secguide and X.mgv6:
>> 
>>   * RFC 4294 – "IPv6 Node Requirements" (N.B., this work is currently
>>     under revision)
> 
> Why not just reference the bis document?

> 
>>   * draft-ietf-6man-node-req-bis (work in progress) – "IPv6 Node
>>     Requirements RFC 4294-bis"


The draft could also say that the working group has reached consensus and has submitted it to the IESG for publication on 25 May 2011.

Bob


>>   * RFC 4864 – "Local Network Protection for IPv6"
>>   * RFC 6092 – "Recommended Simple Security Capabilities in Customer
>>     Premise Equipment (CPE) for Providing Residential IPv6 Internet
>>     Service"
>>   * RFC 6105 – "IPv6 Router Advertisement Guard"
>>   * RFC 6106 – "IPv6 Router Advertisement Options for DNS
>>     Configuration", §7 in particular.
>> 
>> As you are aware, every RFC contains a Security Considerations section.
>> In developing either a implementation or deployment guide, contributors
>> are strongly encouraged to review the RFCs and Internet-Drafts that
>> support any underlying function.
>> 
>> In addition, we bring to your attention the following IETF Working
>> Groups that are working on security-related work of IPv6:
>> 
>> Working Group  Purpose                     Mailing list address
>> Name
>> 
>> 6man           IPv6 Maintenance            ipv6@ietf.org
>> savi           Source Address Validation   savi@ietf.org
>>              Improvements
>> dhc            Dynamic Host Configuration  dhcwg@ietf.org
>> v6ops          IPv6 Operations             v6ops@ietf.org
>> opsec          Operational Security        opsec@ietf.org
>>              Capabilities for an IP
>>              Network
>> 
>> In addition to the above working groups, the Security Area of the IETF
>> maintains a mailing list for general discussion, saag@ietf.org.  We
>> encourage and invite open and informal discussion in these or other
>> relevant IETF fora on this very important topic. As with all IETF
>> working groups, any and all interested parties can choose to directly
>> contribute via the mailing lists above.
>> 
>> As in other areas, the Security Area of the IETF invites SG17 to bring
>> any new-found concerns about IETF protocols to our attention so that as
>> and when we revise our documents we can make appropriate amendments to
>> IETF protocols. In particular, as this planned work matures, we would
>> welcome hearing about it in more detail, perhaps via an invited
>> presentation at a saag meeting or via review of draft documents as may
>> be appropriate.
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops