Re: [sacm] XMPP grid

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sat, 08 November 2014 12:28 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF4EF1A6FF6 for <sacm@ietfa.amsl.com>; Sat, 8 Nov 2014 04:28:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.494
X-Spam-Level:
X-Spam-Status: No, score=-7.494 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594] 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 Ht9f6LelWvG2 for <sacm@ietfa.amsl.com>; Sat, 8 Nov 2014 04:28:07 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C15D21A6FEE for <sacm@ietf.org>; Sat, 8 Nov 2014 04:28:06 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiILACULXlSHCzIm/2dsb2JhbABbgmsjVFkEuAcBAQEBAQEGkyAfCodPAoEbFgEBAQEBAXyEAgEBAQEDAQEBDyg0FwQCAQgNBAQBAQsUCQcnCxQJCAIEARIIGogfAQytYKAUAQEBAQYBAQEBAQEBG4Y4hD2FazgGgyeBHgWSJ4RUiFE9hjESiiGECYN5bIFIgQMBAQE
X-IronPort-AV: E=Sophos;i="5.07,340,1413259200"; d="scan'208";a="79885593"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by de307622-de-outbound.net.avaya.com with ESMTP; 08 Nov 2014 07:28:04 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 08 Nov 2014 07:28:03 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0174.001; Sat, 8 Nov 2014 13:28:02 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] XMPP grid
Thread-Index: AQHP+pBi8aIdmVB4aUSMcrTRu744RpxWqS2w
Date: Sat, 08 Nov 2014 12:28:01 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C8FA2B1@AZ-FFEXMB04.global.avaya.com>
References: <2C9F650D-AD86-421B-B145-0D4E8F297E19@gmail.com>
In-Reply-To: <2C9F650D-AD86-421B-B145-0D4E8F297E19@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sacm/AqN6BMB_Xyrs5N-HEvV4pY4J2_w
Subject: Re: [sacm] XMPP grid
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Nov 2014 12:28:08 -0000

Thanks for the review, Kathleen. 

Do the authors of this I-D plan to present the changes in the latest version at the Monday meeting? I would assume 'yes' but I did not receive any agenda request, and right now the protocols agenda item is TBD. 

Regards,

Dan


> -----Original Message-----
> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Kathleen Moriarty
> Sent: Friday, November 07, 2014 3:40 PM
> To: sacm@ietf.org
> Subject: [sacm] XMPP grid
> 
> Hello,
> 
> I just reviewed the recent version of XMPP grid:
> https://tools.ietf.org/html/draft-salowey-sacm-xmpp-grid-01
> 
> First, thank you for your work on this draft.  It looks very good and I
> appreciate the detailed security considerations section.
> 
> Here are some comments to consider:
> 
> Figure 1 what does dev mean? I didn't see this expanded anywhere, maybe I
> missed it?
> 
> 3.6 2nd bullet, typo NThe
> 
> 6.3.1 set minimum for TLS - 1.2 unless there are reasons why that's not
> possible.
> 
> A reference to the UTA best practices draft for TLS would be good to add in
> this section.  It covers all the decisions admins need to consider (developers
> too).  It's close to finishing up, so it will be published before this draft.
> http://tools.ietf.org/html/draft-ietf-uta-tls-bcp-05
> 
> Http auth has a few newish options for authentication instead of just basic
> and digest, could one of them be an option?  HOBA is about to go into IETF
> last call.
> 6.2.1 - do you want to add a reference to the PM RFC7258?
> 
> 7 privacy section
> It's worth mentioning that the easiest way to protect privacy sensitive data is
> to leave it out in the first place.
> 
> You should add something to cover considerations for End to end crypto. This
> may matter more for any sensitive data that is sent via an alternate protocol
> like if-map.  I'm not as familiar with that protocol as it's been a while since I've
> read the spec.
> 
> For XMPP grid, I think from the flow diagrams, you actually wind up with
> point-to-point data access with no interchanges leveraging the grid until you
> switch to an end-to-end mechanism to transport the structured or
> unstructured data, is that correct?  I just want to make sure that is the case, if
> not, a recommendation for object-level encryption should be added for the
> control plane (common concern in the incident response space, which this
> could be used for as well and SACM has similar considerations for some of
> the data to be transported).
> 
> The draft looks great, thanks.
> 
> Thank you,
> Kathleen
> 
> 
> 
> Sent from my iPhone
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm