Re: [Int-area] Call for adoption of draft-boucadair-intarea-host-identifier-scenarios-04

S Moonesamy <sm+ietf@elandsys.com> Wed, 11 June 2014 19:27 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD8A81A0240 for <int-area@ietfa.amsl.com>; Wed, 11 Jun 2014 12:27:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level:
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=ham
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 4NBBflPGOY1m for <int-area@ietfa.amsl.com>; Wed, 11 Jun 2014 12:27:52 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 50DDD1A01D6 for <int-area@ietf.org>; Wed, 11 Jun 2014 12:27:52 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.141.215]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s5BJRXf8021640 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jun 2014 12:27:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1402514866; x=1402601266; bh=XYZ38mGT/r1xNu25JNE+RR2ydkv9/PgfYjrlfU5xRzE=; h=Date:To:From:Subject:In-Reply-To:References; b=QrxANPH2D0PyiXlLoVS/lw4xR1F5twgKrspRg0oxeMBHpCIast5rTMKhLEeJgIzrk WFxrqkqNpDb38wivVC0Sk3K736mp1IMnDb206dp7c/xrVMomkPsspy7vVPsZ8/GfGR Q6bX0v7P+ktcHmyOVy1NYr6fFU5g9bOSSfLDhCY0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1402514866; x=1402601266; i=@elandsys.com; bh=XYZ38mGT/r1xNu25JNE+RR2ydkv9/PgfYjrlfU5xRzE=; h=Date:To:From:Subject:In-Reply-To:References; b=xajnCNrMD7uc5lvVwOlVyPOeSjjc5JYYz19LhgC67+EgB2NUWVN/nM3NRCqll4H/p nUiBVR7HJG6lM1K7uJl8h9iMmRQzFX7KtOt43lYFzo4HdS0HEmhEKq5aTYIuCJnu8X 2qEsBzmp9Gc4X1l3Cl3AYAXd/d5wlFW4sBFggH08=
Message-Id: <6.2.5.6.2.20140611110655.0a7a54f8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 11 Jun 2014 12:10:17 -0700
To: mohamed.boucadair@orange.com, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, int-area@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <787AE7BB302AE849A7480A190F8B9330016053@OPEXCLILM23.corpora te.adroot.infra.ftgroup>
References: <913383AAA69FF945B8F946018B75898A282C8C39@xmb-rcd-x10.cisco.com> <6.2.5.6.2.20140605081321.0bda1060@resistor.net> <787AE7BB302AE849A7480A190F8B933001417F@OPEXCLILM23.corporate.adroot.infra.ftgroup> <6.2.5.6.2.20140606042634.0baaab20@elandnews.com> <787AE7BB302AE849A7480A190F8B9330016053@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/WAfuNa-XxBennxlXE8NEqmMWZps
Subject: Re: [Int-area] Call for adoption of draft-boucadair-intarea-host-identifier-scenarios-04
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jun 2014 19:27:53 -0000

Hi Med,
At 07:24 11-06-2014, mohamed.boucadair@orange.com wrote:
>   The INTAREA working group
> >previously worked on a RFC about potential solutions for revealing a
> >host identifier.   Are the potential solutions discussed in RFC 6967
> >inadequate?
>
>[Med] The effort in RFC6967 does not ambition to pick a solution but 
>to conduct an analysis effort with a focus on the CGN case. That 
>case is only one among others defined in the scenario draft. 
>Identify and document the use cases is a first step to actually 
>understand the problem we are talking about. This is a contribution 
>to clarify the big picture of this problem space.

I left in my previous comment as it may be easier for the reader to 
understand the discussion.

The previous comment mentioned "potential solutions discussed in RFC 
6967".  In my opinion the above response does not provide an answer 
to the question.

You made an interesting point, i.e. clarify the big picture.  I read 
the RFCs coming from INTAREA.  There was one about "Issues with IP 
Address Sharing" in June 2011.  There is another one about "Analysis 
of Potential Solutions for Revealing a Host Identifier (HOST_ID) in 
Shared Address Deployments" in June 2013.  Now there is a draft about 
"Host Identification: Use Cases".  I haven't seen a discussion of 
that big picture on this mailing list.  My understanding of the 
documents is that the working group is make a case (the word is used 
loosely) for host identification.

>[Med] Privacy is not out of scope as I mentioned in a previous 
>message. Nevertheless, privacy implications may depend on the 
>targeted use case. The considerations in RFC6967 can be completed 
>with new ones if any.

Ok.  I assume that the working group has the expertise and energy to 
do that work.

>[Med] What we declared out of scope is solution-oriented aspects. We 
>wanted to have a very focused document.

This is what I read from the draft:

   "It is out of scope of this document to argue in favor or against the
    use cases listed in the following sub-sections."

That is different from the above response.

I'll wait for the Working Group Chairs to take their decision.

Regards,
S. Moonesamy