Re: [Insipid] Review of draft-ietf-insipid-logme-reqs-02

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 12 June 2015 14:24 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07C3B1ACC82 for <insipid@ietfa.amsl.com>; Fri, 12 Jun 2015 07:24:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 dDUqDXWwxTIt for <insipid@ietfa.amsl.com>; Fri, 12 Jun 2015 07:24:52 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3A9C1AC430 for <insipid@ietf.org>; Fri, 12 Jun 2015 07:24:51 -0700 (PDT)
X-AuditID: c1b4fb3a-f79ec6d000006dc0-38-557aebb292c1
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.125]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id D4.44.28096.2BBEA755; Fri, 12 Jun 2015 16:24:50 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.72]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0210.002; Fri, 12 Jun 2015 16:24:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: [Insipid] Review of draft-ietf-insipid-logme-reqs-02
Thread-Index: AQHQoc9he4+R7vgLMUuxbp7avLo3752ltpKAgAFrcQCAAGyO4IABQQwAgAAjqNA=
Date: Fri, 12 Jun 2015 14:24:49 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D8BF4BE@ESESSMB209.ericsson.se>
References: <55756367.7090109@gmx.com> <7594FB04B1934943A5C02806D1A2204B1D8B6E33@ESESSMB209.ericsson.se> <4A4F136CBD0E0D44AE1EDE36C4CD9D99AEEE2BDC@VOEXM31W.internal.vodafone.com> <7594FB04B1934943A5C02806D1A2204B1D8BDFDB@ESESSMB209.ericsson.se> <4A4F136CBD0E0D44AE1EDE36C4CD9D99AEEE3151@VOEXM31W.internal.vodafone.com>
In-Reply-To: <4A4F136CBD0E0D44AE1EDE36C4CD9D99AEEE3151@VOEXM31W.internal.vodafone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyM+Jvre6m11WhBmsviFnMv/+MyaLv5Rcm ByaPJUt+Mnn0zVjPGMAUxWWTkpqTWZZapG+XwJXxf9NttoIHUhUPr3WwNTCuEu1i5OSQEDCR OP7rCDuELSZx4d56ti5GLg4hgaOMEmdOTGSHcBYzSkx9vJ21i5GDg03AQqL7nzZIg4hAmsT5 7xvAmoUFHCVW9x1jgYg7SUxpvcsEYftJ9B5/wwZiswioStzeeAHM5hXwlTjU/hrMFhI4xiTx 4LotyHhOgTCJr7OSQcKMQPd8P7UGbAyzgLjErSfzmSDuFJBYsuc8M4QtKvHy8T+wyyQEFCWW 98tBlOtJ3Jg6hQ3C1pZYtvA1M8RWQYmTM5+wTGAUnYVk6iwkLbOQtMxC0rKAkWUVo2hxanFx brqRkV5qUWZycXF+nl5easkmRmCMHNzy22oH48HnjocYBTgYlXh4FWyrQoVYE8uKK3MPMUpz sCiJ887YnBcqJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgXFa2NMZazZECdxW/znzxFK/B6mc L6PWBUe3357xbWXjtaipPvz3n0+e3KlsWSHMfWilw6sGUa56QfNzC2xs5dk7Ip8+D9He3z43 ZM+kNqvfHpalUSsfT3Zd82bn1RMB6QzOE3hWBH4/Jhrstmnim0OMp7Nnr6xaWqPTl3jJ1rJH 3v1OqmULwy0lluKMREMt5qLiRACE7ToZcgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/OSGwnUTxAo5zCz-kkKpOg-y5d-g>
Subject: Re: [Insipid] Review of draft-ietf-insipid-logme-reqs-02
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2015 14:24:54 -0000

Hi,

>Thanks Christer, I will make these improvements in the next (-03) version, probably early July.

Great.

Note that the draft submission window will close some time before the IETF Prague meeting, though.

Regards,

Christer


> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: 11 June 2015 18:12
> To: Dawes, Peter, Vodafone Group; insipid@ietf.org
> Subject: RE: [Insipid] Review of draft-ietf-insipid-logme-reqs-02
> 
> Hi Peter,
> 
> See inline.
> 
> Q2 (editorial/technical):
> 
> >> I don't understand REQ4, saying "SIP entities SHOULD log SIP 
> >> requests or responses with a "log me" marker."
> >>
> >> Also, in e.g. REQ6 it is then said that proxies MAY insert the 
> >> marker, which seems to contradict.
> >>
> > REQ4 could be re-written slightly more clearly as "SIP entities 
> > SHOULD log SIP requests or responses that contain a "log me" 
> > marker." The SIP entity checks for the presence of a "log me" marker 
> > and writes any request or response that contains a "log me" marker to a log file.
> 
> I think it would be good to say "SIP entities that support the 
> mechanism SHOULD...", to make it clear that we don't expect certain 
> behaviour from SIP entities that do not support the mechanism. Some 
> people may say it's obvious, but I think it's good to have it explicit 
> :)
> 
> > REQ 6 allows a SIP proxy to insert a "log me" marker to allow the 
> > mechanism to work even if the UE does not support this draft, so 
> > this talks
> about inserting a "log me" marker and not checking for its presence.
> 
> Got it. Thanks for the clarification.
> 
> 
> Q3 (editorial/technical):
> 
> >> Regarding REQ5, does that also apply to UAs that do NOT support the 
> >> mechanism? If so, I think that should be explicitly stated, because 
> >> it will have big impact on the technical solution.
> >>
> > UEs that do not support the mechanism are not expected to echo the 
> > "log me" marker because they don't know about it. However, if the 
> > "log me" marker solution is a header field parameter of the 
> > Session-ID header field, as currently proposed, then I guess that 
> > even UEs that do not
> support inserting a "log me" marker will echo it if it echoes the 
> whole Session-ID header field.
> 
> Sure, but that is irrelevant as far as the requirements are concerned 
> :)
> 
> So, if we don't REQUIRE anything from UAs that don't support the 
> mechanism, I again think it's good to explicitly talk about UAs that 
> support the mechanism.
> 
> Regards,
> 
> Christer
> 
> 
> > -----Original Message-----
> > From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of Georg 
> > Mayer
> > Sent: 8. kesäkuuta 2015 12:42
> > To: insipid@ietf.org
> > Cc: Peter.Dawes@vodafone.com
> > Subject: [Insipid] Review of draft-ietf-insipid-logme-reqs-02
> >
> > Hello,
> >
> > I finally managed to review draft-ietf-insipid-logme-reqs-02. I have 
> > no technical comments on it and support all the requirements therein.
> > In my view the draft can progress as is.
> >
> > Cheers,
> > Georg
> >
> >
> > _______________________________________________
> > insipid mailing list
> > insipid@ietf.org
> > https://www.ietf.org/mailman/listinfo/insipid