Hi Wendy, all,
I think we can first go through a list of all test cases, then we complete all
details.
I post the list below. The cases with * are added or updated by me. I also like
to
serve an editor, if possible.
1. Information Resource Directory
1.1 Test-IRD-1: The Information Resource Directory (IRD) enumerates URIs
at which an ALTO server offers Information Resources.
*1.2 Test-IRD-2 ALTO server delegate IRD to a subdomain.
2. Map Service
2.1 Test-MAPS-1: An ALTO client retrieves a complete network map.
2.2 Test-MAPS-2: An ALTO client retrieves a complete cost map for the
numerical cost mode.
2.3 Test-MAPS-3: An ALTO client retrieves a complete cost map for the
ordinal cost mode.
2.4 Test-MAPS-4: This test is designed to detect a change in the
network map.
3. Map-Filtering Service
*3.1 Test-FILTER-1: An ALTO client sends a request to get a filtered network
map
of PID mypid2.
*3.2 Test-FILTER-2: An ALTO client sends a request to get a filtered cost map
from a source PID to a set of destination PIDs.
*3.3 Test-FILTER-3: An ALTO client requests the cost map subject to
certain constraints.
4. Endpoint Property Service
4.1 Test-EPS-1: An ALTO client retrieves a PID for IPv4 address
192.168.1.23.
4.2 Test-EPS-2: An ALTO client retrieves a PID for IPv4 address
192.168.10.23.
4.3 Test-EPS-3: An ALTO client retrieves a PID for IPv4 address
201.1.13.12.
4.4 Test-EPS-4: An ALTO client retrieves a PID for an IPv4 and IPv6
address.
*4.5 Test-EPS-5: An ALTO client retrieves a Private Endpoint Property for an
IPv4
address.
5. Endpoint Cost Service
5.1 Test-ECS-1: An ALTO client requests cost information between
individual endpoints.
5.2 Test-ECS-2: An ALTO client requests the ranking service for a
source host to a set of destination hosts.
5.3 Test-ECS-3: An ALTO client requests the cost service subject to
certain constraints.
6. Protocol Errors
*6.1 Test-ERR-1: An ALTO client sends a malformed JSON body in the
request --- a missing closing brace ('}'). (E_SYNTAX)
*6.2 Test-ERR-2: An ALTO client sends a malformed request --- the
"dsts" member for the endpoint cost service is missing. (E_MISSING_FIELD)
*6.3 Test-ERR-3: An ALTO client sends a request with an unexpected
type for a JSON value. (E_INVAILD_FIELD_TYPE)
*6.4 Test-ERR-4: An ALTO client sends a request with a wrong value for
a correct field. (E_INVAILD_FIELD_VALUE)
*6.5 Test-ERR-5: An ALTO client sends a request with multiple
errors.
> -----原始邮件-----
> 发件人: "Vijay K. Gurbani" <[email protected]>
> 发送时间: 2015-05-13 00:01:35 (星期三)
> 收件人: "郭华明" <[email protected]>
> 抄送: "Y. Richard Yang" <[email protected]>, "IETF ALTO" <[email protected]>
> 主题: Re: [alto] ALTO implementation interoperability
>
> On 05/11/2015 07:41 PM, 郭华明 wrote:
> > Dear Vijay, Richard,
> >
> > I am interested in this work. I will bring the test cases soon.
>
> Excellent. Please coordinate with the editors of the document with
> regard to bringing new test cases.
>
> Thanks for your time on this!
>
> Cheers,
>
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / [email protected]
> Web: http://ect.bell-labs.com/who/vkg/ | Calendar: http://goo.gl/x3Ogq
--
----------------
Best!
Huaming Guo
China Academy of Information and Communications Technology (CAICT)
No.36 A Nanlishi Road, Xicheng District, Beijing 100037, China
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
