per-entity - Re: [Per-Entity] avoiding dynamic metadata queries
Subject: Per-Entity Metadata Working Group
List archive
- From: Scott Koranda <>
- To: Ian Young <>
- Cc: Tom Scavo <>, Scott Cantor <>, "" <>
- Subject: Re: [Per-Entity] avoiding dynamic metadata queries
- Date: Thu, 11 Aug 2016 12:40:50 -0500
- Ironport-phdr: 9a23:yDq9qh3QKnTWVX97smDT+DRfVm0co7zxezQtwd8ZseseI/ad9pjvdHbS+e9qxAeQG96Eu7QZ0KGP7ujJYi8p39WoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6lX71zMZGw3+OAxpPay1X9eK14Xkn9y1rrzaZU15gye7bvsmLRywhQTYp48Rm4QkN6VnmTXTpX4dQO9R2X8gBlWJlhDw74/k551k6S1Wt/sJ+MtJUKG8dKM9G+8LRA86Onw4sZW4/SLIShGCsz5FCj0b
> I'm not in favour of throwing the baby out with the bathwater, certainly. I
> think the spec needs a way of saying "all of them", but by the same token I
> am not opposed to some change in the wording giving an implementation more
> leeway in its response.
>
> If people have suggested revisions to the text, let me know.
> I am overdue in pushing a new rev of the draft to the IETF
> anyway, I mainly haven't bothered because there were no
> useful changes. If we have some, I can do that fairly
> quickly.
I like the idea of a server being able to say in a compliant
way "no, I will not give you all of them because that is
expensive and I do not have time".
So a developer/deployer has the freedom to not deliver the
full aggregate in order to meet performance requirements.
Scott K
- Re: [Per-Entity] avoiding dynamic metadata queries, Ian Young, 08/10/2016
- Re: [Per-Entity] avoiding dynamic metadata queries, Nick Roy, 08/10/2016
- Re: [Per-Entity] avoiding dynamic metadata queries, Ian Young, 08/10/2016
- RE: [Per-Entity] avoiding dynamic metadata queries, Cantor, Scott, 08/10/2016
- Re: [Per-Entity] avoiding dynamic metadata queries, Scott Koranda, 08/11/2016
- Re: [Per-Entity] avoiding dynamic metadata queries, Nick Roy, 08/10/2016
Archive powered by MHonArc 2.6.19.