Re: [v6ops] Fwd: 82nd IETF DRAFT Agenda

Joel jaeggli <joelja@bogus.com> Thu, 27 October 2011 23:54 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7073E21F8509 for <v6ops@ietfa.amsl.com>; Thu, 27 Oct 2011 16:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.399
X-Spam-Level:
X-Spam-Status: No, score=-99.399 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WDhn7fqxOgj7 for <v6ops@ietfa.amsl.com>; Thu, 27 Oct 2011 16:54:02 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C953021F8507 for <v6ops@ietf.org>; Thu, 27 Oct 2011 16:54:02 -0700 (PDT)
Received: from Zorch.local (64-197-126-83.ip.mcleodusa.net [64.197.126.83] (may be forged)) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p9RNrtTE099585 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 27 Oct 2011 23:53:56 GMT (envelope-from joelja@bogus.com)
Message-ID: <4EA9EF0E.1040909@bogus.com>
Date: Thu, 27 Oct 2011 16:53:50 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Xing Li <xing@cernet.edu.cn>
References: <4EA867C7.3050705@globis.net> <4EA9EDCD.2050502@cernet.edu.cn>
In-Reply-To: <4EA9EDCD.2050502@cernet.edu.cn>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 27 Oct 2011 23:53:56 +0000 (UTC)
Cc: Ray Hunter <v6ops@globis.net>, "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd: 82nd IETF DRAFT Agenda
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Oct 2011 23:54:03 -0000

On 10/27/11 16:48 , Xing Li wrote:
> Due to the IPv4 address depletion, more and more IPv4/IPv6 translators
> are being deployed. We need a guideline for representing
> non-IPv4-translatable address as the source address in ICMP packets.
> Based on our operation experience, allocating a special IPv4 //24 is a
> reasonable choice. If we can move forward, there will be enough time for
> ISPs to update the filters.

with the properties for utilization described in the draft there'd be no
way in hell I'd accept these on the ingress to my network.

> Regards,
> 
> xing
> 
>>
>> Regards,
>> RayH
>>
>>> Subject:
>>> Re: [v6ops] Fwd: 82nd IETF DRAFT Agenda
>>> From:
>>> Warren Kumari <warren@kumari.net>
>>> Date:
>>> Wed, 26 Oct 2011 07:32:35 -0400
>>>
>>> To:
>>> Xing Li <xing@cernet.edu.cn>
>>> CC:
>>> "v6ops@ietf.org WG" <v6ops@ietf.org>, V6ops Chairs
>>> <v6ops-chairs@tools.ietf.org>
>>>
>>> Content-Transfer-Encoding:
>>> quoted-printable
>>> Precedence:
>>> list
>>> MIME-Version:
>>> 1.0 (Apple Message framework v1084)
>>> References:
>>> <20111013211312.B6C7421F8AFF@ietfa.amsl.com>
>>> <619C3B81-1CDC-4341-8180-EC8472864CC0@cisco.com>
>>> <4EA53FB7.6090603@cernet.edu.cn>
>>> In-Reply-To:
>>> <4EA53FB7.6090603@cernet.edu.cn>
>>> Message-ID:
>>> <C8B7882E-F8F0-4E65-AC5C-D8CDA24DC0EC@kumari.net>
>>> Content-Type:
>>> text/plain; charset=utf-8
>>> Message:
>>> 1
>>>
>>>
>>> On Oct 24, 2011, at 6:36 AM, Xing Li wrote:
>>>
>>>   
>>>> > Hi, Fred and All,
>>>> > 
>>>> > 于 2011/10/14 5:52, Fred Baker 写道:
>>>>     
>>>>> >> The initial version of the agenda has been posted. It places v6ops on Wednesday and Friday mornings, a total of 4.5 hours. I personally am satisfied with it, but if folks have issues I can pass them along.
>>>>> >> 
>>>>> >> I'll note that the deadline for -00 drafts is 24 October, and the deadline for updated drafts is a week later. For discussion in the working group meetings, I'm looking for a draft posted after 25 July, with supporting email discussion on the list.
>>>>> >> 
>>>>> >> I'm looking for (and in some cases have seen) commentary on each of:
>>>>> >> 
>>>>> >> -rw-rw-r--  1 fred  fred  13796 Jul 25 23:59 draft-xli-v6ops-ivi-icmp-address-00.txt
>>>>>       
>>>> > 
>>>> > I would like to request that the V6ops WG adopt draft-xli-v6ops-ivi-icmp-address-00.txt as a WG adoption.
>>>> > 
>>>> > The draft describes the operational considerations of mapping ICMPv6 packets through an RFC6145 gateway where the IPv6 address is not directly translatable into an IPv4 address, and requests an IANA Special Purpose IPv4 address allocation (192.70.192.0/24) to allow this address mapping to take place using a protocol-specific designated address block in IPv4.
>>>> > 
>>>>     
>>>
>>> Summary:
>>> I support adoption.
>>>
>>> More words: 
>>> I must admit to being somewhat uncomfortable with the potential for using this space to hide that actual course of a DoS -- yes, this is somewhat addressed in the Security Considerations, but that doesn't actually remove the problem.
>>> That said, the sad fact is that with so many networks not doing BCP38 you already have no faith in the source address of a packet IMO the benefits outweigh the risks.
>>>
>>> W
>>>
>>>   
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops