Re: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis

Paul Kyzivat <pkyzivat@cisco.com> Wed, 25 August 2010 18:01 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 919813A6903 for <sipcore@core3.amsl.com>; Wed, 25 Aug 2010 11:01:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.499
X-Spam-Level:
X-Spam-Status: No, score=-110.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 1uiS9IEwuXWi for <sipcore@core3.amsl.com>; Wed, 25 Aug 2010 11:01:27 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 635EE3A68EF for <sipcore@ietf.org>; Wed, 25 Aug 2010 11:01:27 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADr3dExAZnwM/2dsb2JhbACgPXGhe5wPhTcEigM
X-IronPort-AV: E=Sophos;i="4.56,269,1280707200"; d="scan'208";a="151838248"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 25 Aug 2010 18:01:59 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o7PI1w5t020381; Wed, 25 Aug 2010 18:01:59 GMT
Message-ID: <4C755A96.1090400@cisco.com>
Date: Wed, 25 Aug 2010 14:01:58 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
References: <4C69ADA8.1010802@nostrum.com> <4C753AAA.3030407@nostrum.com> <4C754893.4080202@cisco.com> <AANLkTimBgKC_eZo1FGQWk-vYOTPRzgVZ7opGTj1h_0Zo@mail.gmail.com> <AANLkTik4_bNqiTLtJYxKcqbuiD=MuXY3opuuNahgqmjL@mail.gmail.com>
In-Reply-To: <AANLkTik4_bNqiTLtJYxKcqbuiD=MuXY3opuuNahgqmjL@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "SIPCORE \(Session Initiation Protocol Core\) WG" <sipcore@ietf.org>
Subject: Re: [sipcore] REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Aug 2010 18:01:28 -0000

Mary Barnes wrote:
> Actually, I did respond to that message, per the following:
> http://www.ietf.org/mail-archive/web/sipcore/current/msg03088.html
> 
> (threading in the email archives is no better than my archiving method 
> for emails). 

Hmm. I cannot find that one anywhere in my own archives, and I don't 
recall seeing it. Don't know why. :-(

> That sentence is written within the context of core RFC 3261.  We really didn't get into the RFC 3325 trust domain concept in RFC 4244 - in particular because RFC 3325 is informational.  However, there is an UNLESS later in that section:
> 
> "...,unless the processing entity knows a priori that it can rely on a downstream processing entity within its domain to apply the requested privacy or local policy allows the forwarding."
> 
> So, I will include that same clause in the sentence you are concerned about.

That doesn't do it for me. I think one way or another you need to 
address whether "domain" means "DNS domain" or "trust domain". And if it 
means "trust domain" then of course we need a ref to 3325.

You seem to mean DNS domain, but the kinds of actions you are discussing 
seem more related to 3323 and 3325. ISTM that if you mean DNS domain 
then you mean it based on an assumption that "DNS domain" = "trust domain".

	Thanks,
	Paul

> Thanks,
> Mary. 
> 
> On Wed, Aug 25, 2010 at 11:51 AM, Mary Barnes 
> <mary.ietf.barnes@gmail.com <mailto:mary.ietf.barnes@gmail.com>> wrote:
> 
>     Sorry, I should have replied to that thread, but I didn't think
>     there was a change necessary.  I'll reply now.
> 
>     Mary. 
> 
> 
>     On Wed, Aug 25, 2010 at 11:45 AM, Paul Kyzivat <pkyzivat@cisco.com
>     <mailto:pkyzivat@cisco.com>> wrote:
> 
>         [as individual]
> 
>         There was some discussion on the -00 version back in July that
>         was not, AFAICT, addressed in the -01 version. There is a thread
>         emanating from mary's announcement of the -00 version. The
>         following is a hook into that thread:
> 
>         http://www.ietf.org/mail-archive/web/sipcore/current/msg03056.html
> 
>         It has to do with when privacy should be applied.
> 
>                Thanks,
>                Paul
> 
> 
>         Adam Roach wrote:
> 
> 
>              [as chair]
> 
>             As a reminder, we're just over halfway through this WGLC,
>             and have not yet seen any comments. Please take some time to
>             review this draft.
> 
>             /a
> 
>             On 8/16/10 4:29 PM, Adam Roach - SIPCORE Chair wrote:
> 
> 
>                 [as chair]
> 
>                 A major author of draft-ietf-sipcore-rfc4244bis-01
>                 believes that the document has no remaining open issues,
>                 and is ready for evaluation. Today, we are starting a
>                 two-week working group last call period. This last call
>                 period ends on Tuesday, August 31st.
> 
>                 The latest version of the document can be retrieved here:
> 
>                 http://tools.ietf.org/html/draft-ietf-sipcore-rfc4244bis
> 
>                 Any comments on the document should be sent to the
>                 SIPCORE mailing list.
> 
>                 /a
> 
>                 _______________________________________________
>                 sipcore mailing list
>                 sipcore@ietf.org <mailto:sipcore@ietf.org>
>                 https://www.ietf.org/mailman/listinfo/sipcore
> 
> 
>             _______________________________________________
>             sipcore mailing list
>             sipcore@ietf.org <mailto:sipcore@ietf.org>
>             https://www.ietf.org/mailman/listinfo/sipcore
> 
>         _______________________________________________
>         sipcore mailing list
>         sipcore@ietf.org <mailto:sipcore@ietf.org>
>         https://www.ietf.org/mailman/listinfo/sipcore
> 
> 
>