RE: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10

2010-03-21 Thread Tschofenig, Hannes (NSN - FI/Espoo)
To: Rohan Mahy; Brian Rosen; Hannes Tschofenig; General Area Review Team Cc: Cullen Jennings; IETF-Discussion list Subject: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10 I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen

Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10

2010-03-21 Thread Ben Campbell
; IETF-Discussion list Subject: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10 I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, please see http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html). Please wait

Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10

2010-03-21 Thread Ben Campbell
On Mar 21, 2010, at 3:12 PM, Thomson, Martin wrote: Ben wrote: There's a few ways to handle that: 1) Treat rate-control as an informative reference, and say you're doing something mostly like rate control, but not quite identical. That would require quite a bit more normative language

Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10

2010-03-21 Thread Ben Campbell
; salvatore.lor...@ericsson.com; Cullen Jennings; Rohan Mahy; IETF-Discussion list; General Area Review Team; Hannes Tschofenig Subject: Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10 On Mar 21, 2010, at 3:12 PM, Thomson, Martin wrote: Ben wrote: There's a few

Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10

2010-03-21 Thread Ben Campbell
On Mar 21, 2010, at 3:49 PM, Thomson, Martin wrote: So, the rate control does recognize that the first notify message can be empty or might not contain all state: $3.2: Thus, the first notification might be empty, or certain values might be absent. The text that was originally

RE: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10

2010-03-21 Thread Thomson, Martin
Ben wrote: There's a few ways to handle that: 1) Treat rate-control as an informative reference, and say you're doing something mostly like rate control, but not quite identical. That would require quite a bit more normative language to describe what you're actually doing. 2) Make this

RE: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10

2010-03-21 Thread Tschofenig, Hannes (NSN - FI/Espoo)
; Hannes Tschofenig Subject: Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10 On Mar 21, 2010, at 3:12 PM, Thomson, Martin wrote: Ben wrote: There's a few ways to handle that: 1) Treat rate-control as an informative reference, and say you're doing something mostly like rate

RE: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10

2010-03-21 Thread Thomson, Martin
Ben wrote: I was not under the impression from reading rate-control that that document was modifying 3265 to prevent notifiers from sending an empty notify. But, your suggestion is a reasonable one. Reading the rate-control text you quoted earlier in the thread could lead to the

RE: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10

2010-03-21 Thread Thomson, Martin
); aki.ni...@nokia.com; krisztian.k...@nokia.com; salvatore.lor...@ericsson.com; Cullen Jennings; Rohan Mahy; IETF-Discussion list; General Area Review Team; Hannes Tschofenig Subject: Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10 On Mar 21, 2010, at 3:12 PM, Thomson

Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10

2010-03-09 Thread Ben Campbell
I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, please see http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html). Please wait for direction from your document shepherd or AD before posting a new version of the draft. Document: