The IESG has received a request from the Geographic Location/Privacy WG
(geopriv) to consider the following document:
- 'Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a
Location Uniform Resource Identifier (URI)'
<draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-06-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.
Abstract
This document creates a Dynamic Host Configuration Protocol (DHCP)
Option for transmitting a client's geolocation Uniform Resource
Identifier (URI). This Location URI can then be dereferenced in a
separate transaction by the client or sent to another entity and
dereferenced to learn physically where the client is located.
The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-geopriv-dhcp-lbyr-uri-option/
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-geopriv-dhcp-lbyr-uri-option/ballot/
No IPR declarations have been submitted directly on this I-D.
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
Thursday, May 31, 2012
[Geopriv] I-D Action: draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.
Title : Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI)
Author(s) : James Polk
Filename : draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt
Pages : 13
Date : 2012-05-31
This document creates a Dynamic Host Configuration Protocol (DHCP)
Option for transmitting a client's geolocation Uniform Resource
Identifier (URI). This Location URI can then be dereferenced in a
separate transaction by the client or sent to another entity and
dereferenced to learn physically where the client is located.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt
The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-geopriv-dhcp-lbyr-uri-option/
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
Title : Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI)
Author(s) : James Polk
Filename : draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt
Pages : 13
Date : 2012-05-31
This document creates a Dynamic Host Configuration Protocol (DHCP)
Option for transmitting a client's geolocation Uniform Resource
Identifier (URI). This Location URI can then be dereferenced in a
separate transaction by the client or sent to another entity and
dereferenced to learn physically where the client is located.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-lbyr-uri-option-15.txt
The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-geopriv-dhcp-lbyr-uri-option/
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
Monday, May 14, 2012
Re: [Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-01.txt
The idea of a source and destination is quite subjective when it comes
to NAT traversal. From the perspective of the NAT it is usually the
endpoint behind that initiates the flow (because that's how holes
appear), but where there are two NATs on a flow, the same view is held
by both NATs.
to NAT traversal. From the perspective of the NAT it is usually the
endpoint behind that initiates the flow (because that's how holes
appear), but where there are two NATs on a flow, the same view is held
by both NATs.
e.g.
A -- NATa -- (Internets!) -- NATb -- B
NATa views A as being the source. NATb views B as being the source.
This fits well with what you have since you assume src to be the
default and you are normally talking to something that will share the
perspective bias of the NAT. An explanation of this trap might be
useful.
Extension is easy:
<xs:sequence>
<xs:element name="src" type="flow:flowEndpoint"/>
<xs:element name="dst" type="flow:flowEndpoint"/>
>> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
Nit:
Section 3: s/show/shown/
On 14 May 2012 08:03, Ray Bellis <Ray.Bellis@nominet.org.uk> wrote:
> Following the discussion in Paris and subsequent chats with Martin I've now updated this draft.
>
> The changes are:
>
> - simplified (shorter) XSD
>
> - allowing an IP protocol number to be specified instead
> of "tcp", "udp" etc.
>
> [I considered doing the same for IP version, but I really
> don't see us trying to do IPv10 just yet...]
>
> - adding of an (optional) "target" attribute to the <flow>
> tag to identify which end of the flow is the target of the
> <locationRequest>.
>
> Please review - the draft is short, and I'd love to see it zip straight through the WG and up to the IESG asap.
>
> Ray
>
>> A new version of I-D, draft-bellis-geopriv-flow-identity-01.txt has been successfully submitted by Ray Bellis and posted to the IETF repository.
>>
>> Filename: draft-bellis-geopriv-flow-identity
>> Revision: 01
>> Title: Flow Identity Extension for HELD
>> Creation date: 2012-05-14
>> WG ID: Individual Submission
>> Number of pages: 12
>
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
[Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-01.txt
Following the discussion in Paris and subsequent chats with Martin I've now updated this draft.
The changes are:
- simplified (shorter) XSD
- allowing an IP protocol number to be specified instead
of "tcp", "udp" etc.
[I considered doing the same for IP version, but I really
don't see us trying to do IPv10 just yet...]
- adding of an (optional) "target" attribute to the <flow>
tag to identify which end of the flow is the target of the
<locationRequest>.
Please review - the draft is short, and I'd love to see it zip straight through the WG and up to the IESG asap.
Ray
> A new version of I-D, draft-bellis-geopriv-flow-identity-01.txt has been successfully submitted by Ray Bellis and posted to the IETF repository.
>
> Filename: draft-bellis-geopriv-flow-identity
> Revision: 01
> Title: Flow Identity Extension for HELD
> Creation date: 2012-05-14
> WG ID: Individual Submission
> Number of pages: 12
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
The changes are:
- simplified (shorter) XSD
- allowing an IP protocol number to be specified instead
of "tcp", "udp" etc.
[I considered doing the same for IP version, but I really
don't see us trying to do IPv10 just yet...]
- adding of an (optional) "target" attribute to the <flow>
tag to identify which end of the flow is the target of the
<locationRequest>.
Please review - the draft is short, and I'd love to see it zip straight through the WG and up to the IESG asap.
Ray
> A new version of I-D, draft-bellis-geopriv-flow-identity-01.txt has been successfully submitted by Ray Bellis and posted to the IETF repository.
>
> Filename: draft-bellis-geopriv-flow-identity
> Revision: 01
> Title: Flow Identity Extension for HELD
> Creation date: 2012-05-14
> WG ID: Individual Submission
> Number of pages: 12
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
Monday, May 7, 2012
Re: [Geopriv] I-D Action: draft-ietf-geopriv-deref-protocol-05.txt
This update covers feedback from IESG review.
On 7 May 2012 15:43, <internet-drafts@ietf.org> wrote:
> Title : A Location Dereferencing Protocol Using HELD
> Filename : draft-ietf-geopriv-deref-protocol-05.txt
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
[Geopriv] I-D Action: draft-ietf-geopriv-deref-protocol-05.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.
Title : A Location Dereferencing Protocol Using HELD
Author(s) : James Winterbottom
Hannes Tschofenig
Henning Schulzrinne
Martin Thomson
Filename : draft-ietf-geopriv-deref-protocol-05.txt
Pages : 23
Date : 2012-05-07
This document describes how to use the Hypertext Transfer Protocol
(HTTP) over Transport Layer Security (TLS) as a dereferencing
protocol to resolve a reference to a Presence Information Data Format
Location Object (PIDF-LO). The document assumes that a Location
Recipient possesses a URI that can be used in conjunction with the
HTTP-Enabled Location Delivery (HELD) protocol to request the
location of the Target.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-deref-protocol-05.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-deref-protocol-05.txt
The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-geopriv-deref-protocol/
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
Title : A Location Dereferencing Protocol Using HELD
Author(s) : James Winterbottom
Hannes Tschofenig
Henning Schulzrinne
Martin Thomson
Filename : draft-ietf-geopriv-deref-protocol-05.txt
Pages : 23
Date : 2012-05-07
This document describes how to use the Hypertext Transfer Protocol
(HTTP) over Transport Layer Security (TLS) as a dereferencing
protocol to resolve a reference to a Presence Information Data Format
Location Object (PIDF-LO). The document assumes that a Location
Recipient possesses a URI that can be used in conjunction with the
HTTP-Enabled Location Delivery (HELD) protocol to request the
location of the Target.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-deref-protocol-05.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-geopriv-deref-protocol-05.txt
The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-geopriv-deref-protocol/
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
Subscribe to:
Posts (Atom)