IETF Logo Mail Archive

[XCON] Re: tsv-dir review of draft-ietf-xcon-bfcp-connection-04

Cullen Jennings <fluffy@cisco.com> Thu, 05 July 2007 16:41 UTC

Return-path: <xcon-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6UOO-0001G5-QE; Thu, 05 Jul 2007 12:41:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6UOM-0001FZ-DP; Thu, 05 Jul 2007 12:41:18 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6UNC-0003VY-O4; Thu, 05 Jul 2007 12:41:18 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 05 Jul 2007 09:39:37 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAM66jEarR7PE/2dsb2JhbAA
X-IronPort-AV: i="4.16,504,1175497200"; d="scan'208"; a="177122264:sNHT73603566"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l65GdbUQ022592; Thu, 5 Jul 2007 09:39:37 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82]) by sj-core-1.cisco.com (8.12.10/8.12.6) with SMTP id l65GdZXI026925; Thu, 5 Jul 2007 16:39:35 GMT
In-Reply-To: <F222151D3323874393F83102D614E0550A4D2263@CORPUSMX20A.corp.emc.com>
References: <F222151D3323874393F83102D614E055068B9132@CORPUSMX20A.corp.emc.com> <4675044C.9040004@ericsson.com> <F222151D3323874393F83102D614E055068B96B9@CORPUSMX20A.corp.emc.com> <468CC0CA.7040805@ericsson.com> <F222151D3323874393F83102D614E0550A4D2263@CORPUSMX20A.corp.emc.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <792852CF-42D8-4282-8FE4-61F017DB78DA@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Date: Thu, 05 Jul 2007 09:38:33 -0700
To: Black_David@emc.com
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=998; t=1183653577; x=1184517577; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20tsv-dir=20review=20of=20draft-ietf-xcon-bfcp-connecti on-04 |Sender:=20; bh=8d8YSXlgvJ0N7/698/ZDx+sww1L78jmy/l7hlKQaDXg=; b=j05fgwoYUghS7x2VLvFtGAuFLXmUq2hLDJIncFUl6vMiOXDPND6057uoEEFWENnFBXm+o4sq q7XFiPViC4VYz0+E3M4/knzGvtFkmvYnV9pOKb3naULORiaQtGybQTH6;
Authentication-Results: sj-dkim-4; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: tsv-dir@ietf.org, xcon@ietf.org, Gonzalo.Camarillo@ericsson.com, ietf@ietf.org
Subject: [XCON] Re: tsv-dir review of draft-ietf-xcon-bfcp-connection-04
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
Errors-To: xcon-bounces@ietf.org

David - I put this tracker as a note so we are sure the appropriate  
ADs don't miss it in IESG review.

On Jul 5, 2007, at 6:57 AM, Black_David@emc.com wrote:

> Gonzalo,
>
> The -05 draft looks fine, and I have no problem with leaving comment
> (1) [whether to say something applicable beyond BFCP on the subjects
> of IP address selection and use of SubjectAltName] to the discretion
> of the ADs.
>
> Thanks,
> --David
>
>>
>> Black_David@emc.com wrote:
>>> Gonzalo,
>>>
>>> Most of this looks good; I have a few comments:
>>>
>>> (1) In the two places where there are general recommendations that
>>> 	are not specific to BFCP (IP address selection and use of
>>> 	SubjectAltName in certs in preference to Subject), it would
>>> 	be good to note that these are general recommendations
>>> 	that are not specific to BFCP, **but** please consult your
>>> 	AD on whether and how to do this, as these are cross-area
>>> 	issues in the IETF.  The existing text is ok.

_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon

v2.23.0 | Report a Bug | By Email