Common use of URL Clause in Contracts

URL. A conforming entity SHALL support tel-URLs and SIP-URLs. SIPS URLs MAY also be supported. In the case of SIP/SIPS URIs, the domain part SHALL be a FQDN. Passwords in the userinfo field SHOULD NOT be used and are to be ignored if present.

Appears in 1 contract

Samples: citeseerx.ist.psu.edu

AutoNDA by SimpleDocs

URL. A conforming entity SHALL shall support tel-URLs and SIP-URLs. SIPS URLs MAY also be supported. In the case of SIP/SIPS URIs, the domain part SHALL be a FQDN. Passwords in the userinfo field SHOULD NOT be used are not recommended and are to be ignored if present.

Appears in 1 contract

Samples: citeseerx.ist.psu.edu

URL. A conforming entity SHALL shall support tel-URLs and SIP-URLs. SIPS URLs MAY also shall be supported. In the case of SIP/SIPS URIs, the domain part SHALL be a FQDNsupported if TLS is required (see 3.5). Passwords in the userinfo field SHOULD NOT be used are not recommended and are to be ignored if present.

Appears in 1 contract

Samples: citeseerx.ist.psu.edu

AutoNDA by SimpleDocs

URL. A conforming entity SHALL shall support tel-URLs and SIP-URLs. SIPS URLs MAY shall also be supported. In the case of SIP/SIPS URIs, the domain part SHALL supported if TLS is to be a FQDNused (see section 3.5). Passwords in the userinfo field SHOULD NOT be used are not recommended and are to be ignored if present.

Appears in 1 contract

Samples: citeseerx.ist.psu.edu

Time is Money Join Law Insider Premium to draft better contracts faster.