Re: [salud] Review comments on draft-ietf-salud-alert-info-urns-13

Christer Holmberg <> Tue, 09 September 2014 17:45 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 16CFA1A8757 for <>; Tue, 9 Sep 2014 10:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9E-A1VNvuuXy for <>; Tue, 9 Sep 2014 10:45:05 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 166E71A8737 for <>; Tue, 9 Sep 2014 10:44:53 -0700 (PDT)
X-AuditID: c1b4fb25-f791c6d00000617b-39-540f3c93e21d
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id EA.DF.24955.39C3F045; Tue, 9 Sep 2014 19:44:52 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Tue, 9 Sep 2014 19:44:51 +0200
From: Christer Holmberg <>
To: Laura Liess <>
Thread-Topic: [salud] Review comments on draft-ietf-salud-alert-info-urns-13
Thread-Index: Ac/IFf+gMZjC49hSQeiq/vmrqzhpOAECnhIAAA0sVGI=
Date: Tue, 9 Sep 2014 17:44:50 +0000
Message-ID: <>
References: <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D4411D8ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42KZGfG3RneKDX+IwYl97BZzrhha3O04wOjA 5PF0wmR2jyVLfjIFMEVx2aSk5mSWpRbp2yVwZbT+fsta8C+hYunxnawNjL+Duxg5OCQETCT2 fmbvYuQEMsUkLtxbz9bFyMUhJHCUUWLJkdvsEM5iRom+x7NYQRrYBCwkuv9pgzSICOhLnOj7 CNbMLKAqsff2EiYQW1jAW2L5/T/MEDU+Ere3v4WyrSR+nL7EBmKzCKhIfPm9ghXE5hXwlejY +48JYtckRolJnyeANXAKBEocurYMrIgR6Lrvp9YwQSwTl7j1ZD4TxNUCEkv2nGeGsEUlXj7+ xwphK0q0P21ghKjPlzj5/CgzxDJBiZMzn7BMYBSdhWTULCRls5CUQcQNJN6fm88MYWtLLFv4 GsrWl9j45SwjsvgCRvZVjKLFqcVJuelGxnqpRZnJxcX5eXp5qSWbGIHRdnDLb9UdjJffOB5i FOBgVOLhTZzOFyLEmlhWXJl7iFGag0VJnHfhuXnBQgLpiSWp2ampBalF8UWlOanFhxiZODil GhgTcwP3BV8RWVnmLjdpW2Ni5ddpMYXvO0+c0ewxCzL5Jjz54+fnv6UEOEOEsvlyn76RU9Gr lP4/yc19nv2br2b6M9Z+fba+YPL/5hXT42IZm4sPW9WY8llev+Vzae+amlecvKuyFtUpXlaS trR62S9kkL3nsuS/bUpL+Ged85zI+2Hq5996to+UWIozEg21mIuKEwHtMO4GlwIAAA==
Cc: "" <>
Subject: Re: [salud] Review comments on draft-ietf-salud-alert-info-urns-13
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 09 Sep 2014 17:45:07 -0000

Hi Laura,

>Please find below the text changes according to your comments Q4-1_1  and Q4-2_1.  Is the text OK for you?

I don't find any text :)

> I am not sure what we should do concerning the comment QG_1.  IMO, usually RFCs do not mention all possible scenarios or use cases which may occur. The content of an Alert-Info
> applies just to the message, there is no text saying in any way that the content of the Alert-Info applies to a dialog or transaction.
> Additionaly, if we add text and mention these use cases, I think people will ask for concrete examples, then for message flows and so on, so that finishing the draft will take another year...
> There is also nothing we can do here for a UA receiving different Alert-Info in two non-100 provisional reasponses, we have no rules on how the UA has to handle them, this is implementation dependent anyway.
> So, my personal opinion is to leave this out.

I think a simple note, saying that depending on the use-case/service, subsequent non-100 provisional responses might contain different values. Otherwise I am pretty sure that people, sooner or later, will argue whether it is allowed or not...





As it is now allowed to use the Alert-Info header field in any non-100 provisional response, I assume the value could actually change from one
response to another.

Eventhough RFC3261 does not explicitly forbid it, perhaps it would be good to explicitly mention that in this draft, because I assume there could be use cases where
e.g. one value is received in a 181, and another value in a subsequent 180.


Section 4.1:


                This is pure editorial, but for alignment purpose I suggest to change “in all provisional responses…” to “in any non-100 provisional response…”


Section 4.2:


This section is below the “Updates to RFC 3261” section, but it is unclear exactly what is updated.

The first paragraph of section 20.4/RFC 3261 already says that a proxy can insert a A-I header. If you want to explicitly say
that a proxy can also modify an existing header, shouldn’t that be text that you add to e.g. the same paragraph?




salud mailing list<>