On 5/12/15 10:27 AM, CALME, Jim (Jim)** CTR ** wrote:
Hi Paul,
Would it be feasible to use a "data" URL scheme as defined by RFC 2397?
data:[<mediatype>][;base64],<data>
With this syntax, the “mediatype” and “base64” are optional and may be
omitted leaving the “,<data>” available for carrying information as an
alternative to the Alert-Info generic-param.
The above is *possible* syntactically. I don't think anyone can raise an
argument that using it in a proprietary implementation would violate
anything. But you would never be able to get a draft that proposed such
a usage approved.
Though I would agree that depending on the application, there may be a
better alternative.
Again I have to ask what the use case is. Having an alert-info with a
parameter and no URI makes no sense to me. The most likely reason I can
think for wanting to do that is covered by RFC7462.
Thanks,
Paul
Thanks,
Jim
-----Original Message-----
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of
Paul Kyzivat
Sent: Tuesday, May 12, 2015 9:12 AM
To: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] URI value mandatory for Alert-Info?
On 5/11/15 9:12 PM, Alex Balashov wrote:
> Hello,
>
> The ABNF grammar for Alert-Info is:
>
> Alert-Info = "Alert-Info" HCOLON alert-param *(COMMA alert-param)
> alert-param = LAQUOT absoluteURI RAQUOT *( SEMI generic-param )
>
> I have an application that seems to utilise just a generic-param
> without a URI. However, I don't see any */? quantifiers for
> absoluteURI which suggest that it's optional:
>
> absoluteURI = scheme ":" ( hier-part / opaque-part )
>
> Maybe it's a failure on my part to properly understand ABNF, however.
>
> My fundamental question is: is there any grammatically acceptable way
> to have an Alert-Info header value consisting of no URI and just a
> generic-param, e.g.
>
> Alert-Info: ;internal=xyz
> Alert-Info: <>;internal=xyz
No there isn't. There was no intent to allow that.
Can you say more about what you are trying to accomplish? It sounds like
an abuse of Alert-Info. If you explain, maybe we can find a way to
achieve your intent.
Thanks,
Paul
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
<mailto:Sip-implementors@lists.cs.columbia.edu>
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
