
From hosnieh@iknowlaws.de  Sun Feb  9 08:42:26 2014
Return-Path: <hosnieh@iknowlaws.de>
X-Original-To: secauth@ietfa.amsl.com
Delivered-To: secauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE1371A0326 for <secauth@ietfa.amsl.com>; Sun,  9 Feb 2014 08:42:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] 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 5KShtkd4HN8Z for <secauth@ietfa.amsl.com>; Sun,  9 Feb 2014 08:42:24 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id 3892D1A0184 for <secauth@ietf.org>; Sun,  9 Feb 2014 08:42:24 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 7AC0523E24BF for <secauth@ietf.org>; Sun,  9 Feb 2014 16:42:23 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w7h45nuYstdq for <secauth@ietf.org>; Sun,  9 Feb 2014 17:42:22 +0100 (CET)
Received: from kopoli (g225119174.adsl.alicedsl.de [92.225.119.174]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id 7627623E24BC for <secauth@ietf.org>; Sun,  9 Feb 2014 17:42:22 +0100 (CET)
From: "Hosnieh Rafiee" <hosnieh@iknowlaws.de>
To: <secauth@ietf.org>
Date: Sun, 9 Feb 2014 17:42:17 +0100
Message-ID: <000001cf25b5$e528d340$af7a79c0$@iknowlaws.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8lteTJ0W9xnYnaSt20tBgd5XwTiA==
Content-Language: en-us
Subject: [Secauth] requirement draft
X-BeenThere: secauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Omni-purpose Network-layer based Secure Authentication non-working group discussion list <secauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secauth>, <mailto:secauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secauth/>
List-Post: <mailto:secauth@ietf.org>
List-Help: <mailto:secauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secauth>, <mailto:secauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Feb 2014 16:42:26 -0000

Do folks think that if we write down a drafts contains all steps and all
requirements, it helps for understanding the process? 
One problem I can see here is that since some of the discussion was in
separate messages, it was not easy to follow the cases. However, I tried to
summarize the things. If this is the problem, I try to write down a draft
and share it with you here so that others can contribute as well. Jerome
Introduced good resources that we can also use them. 

Please don't keep silent and contribute and share your ideas. I appreciate
your active involvement.

Smile,
Hosnieh





From hsantos@isdg.net  Sun Feb  9 17:15:52 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: secauth@ietfa.amsl.com
Delivered-To: secauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E23DA1A0658 for <secauth@ietfa.amsl.com>; Sun,  9 Feb 2014 17:15:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level: 
X-Spam-Status: No, score=-102.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 abpOZokg8LuM for <secauth@ietfa.amsl.com>; Sun,  9 Feb 2014 17:15:49 -0800 (PST)
Received: from news.winserver.com (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5D2561A0647 for <secauth@ietf.org>; Sun,  9 Feb 2014 17:15:48 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1200; t=1391994946; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=wb/mN6h91kjH0UcoYMUnVbsICmc=; b=M+n1K1QvA6rjXqUwurc1 oBEhnf4/GrQ/MKCCD3lKLhDduvGTNZ5N6WscQ7GZtepDWK/g9G28V/JUfn2I2PE7 zu6bi4jTihQXrYjdl2KU05TqU3n61OaHRNMTdCWtKFT5m1uBU4C5VhQ0AXbbfXwG aVhKDze0TrRarQ5wkAdIPEo=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for secauth@ietf.org; Sun, 09 Feb 2014 20:15:46 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1277423102.137.4820; Sun, 09 Feb 2014 20:15:46 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1200; t=1391994337; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=kjUpngl eVRV89DSkuKXNlnEN79qJcBTQ4kqpLgx/I5k=; b=NGXSzUfkfwOa5YCl3QEQ+ug BKOXrN8a1neTOBDKDbswMHurNk1uAnPaTRxJslOMXIQRn4vleW3wmRakz0a+2MiU j62PlP2O5Rd29XBT0v8zj7pXuCbJ7n67R9qfg1daP30Kd7HhhzmI8WsBrpAjs9qD p8cwZBEFFu0/YEHpSD4k=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for secauth@ietf.org; Sun, 09 Feb 2014 20:05:36 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 723715662.9.232; Sun, 09 Feb 2014 20:05:36 -0500
Message-ID: <52F8283F.5060405@isdg.net>
Date: Sun, 09 Feb 2014 20:15:43 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Hosnieh Rafiee <hosnieh@iknowlaws.de>
References: <000001cf25b5$e528d340$af7a79c0$@iknowlaws.de>
In-Reply-To: <000001cf25b5$e528d340$af7a79c0$@iknowlaws.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: secauth@ietf.org
Subject: Re: [Secauth] requirement draft
X-BeenThere: secauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Omni-purpose Network-layer based Secure Authentication non-working group discussion list <secauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secauth>, <mailto:secauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secauth/>
List-Post: <mailto:secauth@ietf.org>
List-Help: <mailto:secauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secauth>, <mailto:secauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 01:15:53 -0000

I'm not sure what this group or you are looking for that isn't 
repeating what is already done, that isn't proprietary in nature and 
whether this is a project research or "product" development effort. 
Sounds more like the latter.

What problem(s) was we solving, addressing?

A draft of whatever effort is being attempted would be a good start.

On 2/9/2014 11:42 AM, Hosnieh Rafiee wrote:
> Do folks think that if we write down a drafts contains all steps and all
> requirements, it helps for understanding the process?
> One problem I can see here is that since some of the discussion was in
> separate messages, it was not easy to follow the cases. However, I tried to
> summarize the things. If this is the problem, I try to write down a draft
> and share it with you here so that others can contribute as well. Jerome
> Introduced good resources that we can also use them.
>
> Please don't keep silent and contribute and share your ideas. I appreciate
> your active involvement.
>
> Smile,
> Hosnieh
>
>
>
>
> _______________________________________________
> Secauth mailing list
> Secauth@ietf.org
> https://www.ietf.org/mailman/listinfo/secauth
>
>

-- 
HLS



From nobody Thu Feb 13 13:47:14 2014
Return-Path: <hosnieh@iknowlaws.de>
X-Original-To: secauth@ietfa.amsl.com
Delivered-To: secauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C680E1A00A6 for <secauth@ietfa.amsl.com>; Thu, 13 Feb 2014 13:47:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 y9xmH8Fhz4KS for <secauth@ietfa.amsl.com>; Thu, 13 Feb 2014 13:47:10 -0800 (PST)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) by ietfa.amsl.com (Postfix) with ESMTP id 90DFE1A0055 for <secauth@ietf.org>; Thu, 13 Feb 2014 13:47:10 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id C0E4B23E24BF; Thu, 13 Feb 2014 21:47:08 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i8LSytgvaD-5; Thu, 13 Feb 2014 22:47:06 +0100 (CET)
Received: from kopoli (g225189131.adsl.alicedsl.de [92.225.189.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id 7C9CA23E24BC; Thu, 13 Feb 2014 22:47:06 +0100 (CET)
From: "Hosnieh Rafiee" <hosnieh@iknowlaws.de>
To: "'Hector Santos'" <hsantos@isdg.net>
References: <000001cf25b5$e528d340$af7a79c0$@iknowlaws.de> <52F8283F.5060405@isdg.net>
In-Reply-To: <52F8283F.5060405@isdg.net>
Date: Thu, 13 Feb 2014 22:47:06 +0100
Message-ID: <019201cf2905$23e99680$6bbcc380$@iknowlaws.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGpn28Xeg1snWW5Culz0pBxTsoXswLBF2YCmui+nRA=
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/p_F0M16UpFXBzbQyyphppJftaBg
Cc: secauth@ietf.org
Subject: Re: [Secauth] requirement draft
X-BeenThere: secauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Omni-purpose Network-layer based Secure Authentication non-working group discussion list <secauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secauth>, <mailto:secauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secauth/>
List-Post: <mailto:secauth@ietf.org>
List-Help: <mailto:secauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secauth>, <mailto:secauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 21:47:14 -0000

> I'm not sure what this group or you are looking for that isn't repeating
what is
> already done, that isn't proprietary in nature and whether this is a
project
> research or "product" development effort.

My purpose is actually to use one of the existing drafts available in
network layer for securing the network layer and integrate this approach
with other existing approaches to provide a robust authentication mechanism.
But since we also need to think about IPv4 enabled devices because of 90% of
devices on the internet that use IPv4, we need to manipulate that draft to
also consider the support of iPv4. This is not a research project and it is
individual initiation. Nevertheless, it might involve some research to find
the best way. we want to have an outcome as a product or an implementation.
I am also thinking about having a BoF in next IETF to seriously working on
that to make it complete. But before that we need to move forward otherwise
there will be no outcome.

I think that this means of authentication should be as flexible that can be
used with DNS, web servers and other protocols.

> What problem(s) was we solving, addressing?

We want to find a unique secure approach for authentication.  We want to use
the methods available in network layer and integrate it with the methods
available in other layer, especially the application layer or come up with
completely new feature.

I am preparing a draft. Probably when I started some sections, I will try to
share it and use google document so that others can also include their ideas
or comments. I do not think I can finish it this week because of the cutoff
date for drafts. but will try to initiate the work. 

Thanks,
Hosnieh


> -----Original Message-----
> From: Secauth [mailto:secauth-bounces@ietf.org] On Behalf Of Hector Santos
> Sent: Monday, February 10, 2014 2:16 AM
> To: Hosnieh Rafiee
> Cc: secauth@ietf.org
> Subject: Re: [Secauth] requirement draft
> 
> I'm not sure what this group or you are looking for that isn't repeating
what is
> already done, that isn't proprietary in nature and whether this is a
project
> research or "product" development effort.
> Sounds more like the latter.
> 
> What problem(s) was we solving, addressing?
> 
> A draft of whatever effort is being attempted would be a good start.
> 
> On 2/9/2014 11:42 AM, Hosnieh Rafiee wrote:
> > Do folks think that if we write down a drafts contains all steps and
> > all requirements, it helps for understanding the process?
> > One problem I can see here is that since some of the discussion was in
> > separate messages, it was not easy to follow the cases. However, I
> > tried to summarize the things. If this is the problem, I try to write
> > down a draft and share it with you here so that others can contribute
> > as well. Jerome Introduced good resources that we can also use them.
> >
> > Please don't keep silent and contribute and share your ideas. I
> > appreciate your active involvement.
> >
> > Smile,
> > Hosnieh
> >
> >
> >
> >
> > _______________________________________________
> > Secauth mailing list
> > Secauth@ietf.org
> > https://www.ietf.org/mailman/listinfo/secauth
> >
> >
> 
> --
> HLS
> 
> 
> _______________________________________________
> Secauth mailing list
> Secauth@ietf.org
> https://www.ietf.org/mailman/listinfo/secauth

