Re: [earlywarning] Comments on draft-schulzrinne-atoca-requirements-00

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Tue, 20 July 2010 19:21 UTC

Return-Path: <Hannes.Tschofenig@gmx.net>
X-Original-To: earlywarning@core3.amsl.com
Delivered-To: earlywarning@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E5243A6BC9 for <earlywarning@core3.amsl.com>; Tue, 20 Jul 2010 12:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9EsRIaJqZ8C for <earlywarning@core3.amsl.com>; Tue, 20 Jul 2010 12:21:32 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 734703A6893 for <earlywarning@ietf.org>; Tue, 20 Jul 2010 12:21:30 -0700 (PDT)
Received: (qmail 707 invoked by uid 0); 20 Jul 2010 19:21:45 -0000
Received: from 213.162.68.166 by www053.gmx.net with HTTP; Tue, 20 Jul 2010 21:21:45 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Date: Tue, 20 Jul 2010 21:21:45 +0200
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
In-Reply-To: <4C45EDC2.9000104@netmagic.com>
Message-ID: <20100720192145.286460@gmx.net>
MIME-Version: 1.0
References: <8B0A9FCBB9832F43971E38010638454F03E9DCD3B0@SISPE7MB1.commscope.com> <4C403CFE.4020208@netmagic.com> <4C45EBEE.9030509@gmx.net> <4C45EDC2.9000104@netmagic.com>
To: trutkowski@netmagic.com
X-Authenticated: #29516787
X-Flags: 0001
X-Mailer: WWW-Mail 6100 (Global Message Exchange)
X-Priority: 3
X-Provags-ID: V01U2FsdGVkX1+6CIZpfJq6ND8XkbHiwPLU3vAuEjQbXTrPRApmRr njeiEtU5TcJJg6Fs/4h0EzkSK5wZQVhxwFmw==
Content-Transfer-Encoding: 8bit
X-GMX-UID: HpI3bIIOeSEqTJIAqXUhZQZ+IGRvbwDg
X-FuHaFi: 0.67000000000000004
Cc: hannes.tschofenig@nsn.com, earlywarning@ietf.org
Subject: Re: [earlywarning] Comments on draft-schulzrinne-atoca-requirements-00
X-BeenThere: earlywarning@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for Authority-to-Individuals \(Early Warning\) Emergency " <earlywarning.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/earlywarning>
List-Post: <mailto:earlywarning@ietf.org>
List-Help: <mailto:earlywarning-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 19:21:33 -0000

Hi Tony, 

When I look at the available sites that offer CAP alerts then I see email alike identifiers (rather than OIDs). 

I wonder whether using OID was a deployment friendly choice. 

Anyway, someone will have to figure out how these OIDs in the CAP alerts relate to signatures protecting CAP alerts. 

Still, this has nothing to do with the transport since the identity in the cert, the content of the sender element of the CAP alert, and the identity in the SIP messages (From field) are less like to all match...

Ciao
Hannes
 

>   On 7/20/2010 2:33 PM, Hannes Tschofenig wrote:
> >
> > Since the work in this group only focuses on the transport 
> > of alerts rather than the actual content of the alerts we 
> > should not be impacted.
> 
> Dear Hannes,
> 
> Probably...except note that the conceptualization of
> the early warning OID namespace includes tagging for
> all objects, including messages as well as organization
> entities.  There is also an ongoing discussion about
> the desirability of binding the identifiers to EVcerts.
> So components of this work could affect transport
> layers/protocols.
> 
> --tony