RE: RE: [Geopriv] Does Location-Conveyance have an HTTPdereferencemechanism defined

I'm OK as long as the ABNF includes the AbsoluteURI option and the text
does not say anything specifically about excluding HTTP (or any other
form of URI).

I've attempted to point out previously that the URI doesn't actually
convey anything about whether the geopriv rules are going to be
respected or not. It's actually a geopriv rule that those rules be
respected so it's superfluous, and out of scope, to also require the
statement in a SIP conveyance document.

AbsoluteURI as a generic form, encompasses sip etc. anyway, so it's also
superfluous to include those in the ABNF. However, it's also a harmless
waste of space. If Brian is keen to include them for some reason, and as
long as neither the text nor the ABNF bias the specification toward
those forms in any way, then there are certainly better things to lose
sleep over.

Cheers,
Martin

> -----Original Message-----
> From: Andrew Newton [mailto:[email protected]]
> Sent: Tuesday, 1 August 2006 11:15 AM
> To: Winterbottom, James
> Cc: IETF SIP List; Rosen, Brian; GEOPRIV
> Subject: Re: [Sip] RE: [Geopriv] Does Location-Conveyance have an
> HTTPdereferencemechanism defined
> 
> 
> On Jul 31, 2006, at 9:11 PM, Winterbottom, James wrote:
> 
> > Hi Andy,
> >
> > That is all I have asked for, do not constrain the ABNF. If "how I
> > use HTTP as a reference" goes in a different document that is fine
> > providing the ABNF is not constrained in the conveyance
> > specification. This is not how I read Brian's statement below:
> >
> > "This is NOT the discussion of what the ABNF of the location header
> > looks
> > like (although it would NOT have http/https in it for sure if we
agree
> > that an HTTP dereference protocol is a separate draft)."
> >
> > Which to me clearly says the ABNF will be restrict to exclude HTTP/
> > HTTPS if there is agreement that the conveyance draft doesn't have
> > specific text on how to deference an HTTP reference.
> >
> > Cheers
> > James
> 
> Please keep in mind that this does not stop the draft from using MUST/
> SHOULD language from stipulating "the URI MUST be a GEOPRIV standards
> track using protocol."
> 
> -andy
> 
> _______________________________________________
> Geopriv mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/geopriv

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip