Search results
From RFC-Wiki
- "about", "preview", "privacy-policy", "terms-of-service", and "type". == "privacy-policy" ==8 KB (1,205 words) - 21:11, 1 October 2020
- Privacy and Accuracy Issues in Network Information Center The purpose of this document is to consider the privacy and accuracy8 KB (1,127 words) - 21:41, 29 September 2020
- User-Agent-Driven Privacy Mechanism for SIP privacy service defined in [[RFC3323|RFC 3323]].19 KB (2,887 words) - 16:01, 14 October 2020
- UNINETT PCA Policy Statements 5.4 Measures taken to protect the privacy of any15 KB (2,370 words) - 11:15, 19 October 2020
- Guidelines for Using the Privacy Mechanism for SIP the privacy mechanism for the Session Initiation Protocol (SIP) that44 KB (6,412 words) - 17:29, 11 October 2020
- Initial Assignment for the Content Security Policy Directives Registry (IANA) registry for Content Security Policy directives and populates8 KB (1,015 words) - 14:00, 2 October 2020
- If the URI is a sip: or sips: URI, then depending on the local policy If the URI is a tel: URI, then depending on the local policy of the18 KB (2,728 words) - 23:51, 3 October 2020
- SD-10 Security & Privacy: Policy & Services SD-10 describes the NADF policy toward security and privacy.6 KB (767 words) - 21:46, 29 September 2020
- SD-10 Security & Privacy: Policy & Services SD-10 describes the NADF policy toward security and privacy.6 KB (785 words) - 22:19, 29 September 2020
- == Pervasive Monitoring Is a Widespread Attack on Privacy == the privacy of Internet users and organisations. The IETF community12 KB (1,730 words) - 04:07, 2 October 2020
- privacy mechanisms to the identity problem. The use of these of such information. This document does NOT offer a general privacy29 KB (4,361 words) - 23:52, 3 October 2020
- privacy. Each country has its own set of laws and practices. === Data Privacy ===14 KB (1,890 words) - 17:34, 19 October 2020
- enhancing TCP communications with privacy and authentication. TLS is based on local policy. For instance, if TLS was being used for16 KB (2,598 words) - 21:35, 3 October 2020
- Privacy-Method "Simple Masking" Privacy-Method "DES-CBC over Mask"31 KB (4,256 words) - 21:29, 30 September 2020
- This memo is a statement of policy by the Internet Activities Board IAB Statement of Policy4 KB (583 words) - 15:41, 15 October 2020
- architecture. Section 3 discusses OPES security and privacy dispatcher constitutes an enhanced policy enforcement point, where29 KB (3,704 words) - 09:52, 4 October 2020
- It is considered a violation of the privacy of the initiator and the particular, it is a violation of privacy to divulge, either directly10 KB (1,472 words) - 08:55, 18 October 2020
- A Privacy Mechanism for the Session Initiation Protocol (SIP) Protocol (SIP) in support of privacy. Specifically, guidelines are46 KB (7,169 words) - 23:50, 3 October 2020
- Distributing Address Selection Policy Using DHCPv6 configure the address selection policy information. This document22 KB (3,026 words) - 00:31, 2 October 2020
- For privacy considerations, it might be the policy of a report matter of local policy. That specification does admonish generators13 KB (1,910 words) - 14:51, 1 October 2020
- which introduces the Privacy header field. The Privacy header field identity. [[RFC3325|RFC 3325]] also defined the 'id' value for the Privacy13 KB (1,925 words) - 22:26, 5 October 2020
- privacy extensions enabled for generating the IPv6 address (e.g., be achieved whatever the port assignment policy enforced by the AFTR17 KB (2,525 words) - 14:43, 2 October 2020
- Location Configuration Extensions for Policy Management inspect or set the privacy rules that are applied to the URIs they34 KB (5,042 words) - 02:56, 2 October 2020
- Implementing Company Classification Policy This document discusses how company security policy for data24 KB (3,216 words) - 19:48, 3 October 2020
- diversion information. In addition, an interworking policy is If previous policy recommendations are applied, the chronological46 KB (5,650 words) - 02:18, 22 October 2020
- discovery of policy or other information about a host ("site-wide likewise, the Platform for Privacy Preferences [W3C.REC-P3P-20020416]11 KB (1,562 words) - 16:04, 14 October 2020
- 3.7. Improper Enforcement of Privacy and Security Policy . . 11 Policy Enforcement Points, and Policy Decision Points [3], and along26 KB (3,814 words) - 09:54, 4 October 2020
- security policy is disobeyed or otherwise breached. The purpose of system event in which the system's security policy is disobeyed or15 KB (2,161 words) - 21:58, 3 October 2020
- 3. To apply privacy, entries were anonymized rather than removed. === Privacy Considerations ===58 KB (7,377 words) - 09:42, 2 October 2020
- Policy, Authorization, and Enforcement Requirements This document describes policy, authorization, and enforcement32 KB (4,713 words) - 09:55, 4 October 2020
- operator with no policy regarding differentiated or tiered access to depending on policy and need." Clients have to be identified and25 KB (3,572 words) - 08:26, 2 October 2020
- Peer Network. However, due to privacy constraints that enable a to share privacy information between them. This will enable15 KB (2,330 words) - 16:49, 11 October 2020
- managing privacy preferences. The large number of specifications can o Privacy and policy, which are documents for expressing privacy31 KB (4,208 words) - 21:24, 1 October 2020
- based on Common Policy [[RFC4745]], an XML document format for expressing privacy preferences.23 KB (3,175 words) - 17:08, 11 October 2020
- policy can state that the rights to disconnect from and to invite to supplementary requirements for conferencing policy, media mixing and20 KB (2,862 words) - 17:46, 4 October 2020
- Security is understood to include protection of the privacy of Another aspect of this part of the policy is that users are20 KB (2,723 words) - 14:04, 16 October 2020
- Another example would be a privacy service proxy [[RFC3323]] performing the 'header' privacy function.18 KB (2,799 words) - 00:47, 2 October 2020
- Integrity, Privacy, and Security SMTP and mail message adaptation by OPES systems and about privacy25 KB (3,766 words) - 18:59, 5 October 2020
- The TLS protocol offers integrity- and privacy-protected exchanges KDC-REP are sent without integrity or privacy protection in14 KB (1,961 words) - 08:12, 1 October 2020
- IAB Architectural and Policy Considerations for some architectural and policy issues related to the chartering of37 KB (5,721 words) - 22:14, 3 October 2020
- Implementation, and Policy Considerations use and privacy issues, including our efforts to inform sites18 KB (2,492 words) - 14:03, 16 October 2020
- | Policy `. | limits the policy options available when the "Authorization by Access42 KB (5,566 words) - 17:59, 1 October 2020
- passwords), so a privacy layer which is not tightly bound to user === Privacy Operational Mode Security Requirements ===28 KB (4,011 words) - 00:34, 20 October 2020
- [[RFC4119]]) carries both location information (LI) and policy The policy carried along with LI allows the Rule Maker to restrict,24 KB (3,716 words) - 21:50, 11 October 2020
- In the framework, an authorization policy is a set of rules. Each watcher, and as such, defines a privacy filtering operation. [8]54 KB (7,937 words) - 21:21, 5 October 2020
- 4.5.1. Example with Privacy Header for Entire 4.5.2. Example with Privacy Header for Specific83 KB (11,131 words) - 17:45, 4 October 2020
- o privacy, o a single privacy protocol and associated parameters by68 KB (9,431 words) - 14:13, 16 October 2020
- diversion-limit | diversion-privacy | diversion-privacy = "privacy" "=" ( "full" | "name" |91 KB (7,766 words) - 16:06, 14 October 2020
- IETF Policy on Wiretapping numerous jurisdictions with numerous requirements for privacy. In16 KB (2,575 words) - 14:27, 3 October 2020
- on local policy. (See the "Security Considerations" section for local policy the Responder can elect to silently discard the query or26 KB (4,049 words) - 13:31, 5 October 2020
- DNS does not make policy decisions about the records it shares with is a cause for some privacy considerations.11 KB (1,650 words) - 12:08, 4 October 2020
- -- the protocol without privacy -- the DES Privacy Protocol [4]69 KB (6,515 words) - 23:18, 16 October 2020
- server in violation of either endpoint's security and privacy policy, === Privacy ===23 KB (3,292 words) - 09:53, 4 October 2020
- 4. Privacy Considerations identifier. This enables the authorization server to apply policy as24 KB (3,456 words) - 10:55, 30 October 2020
- conference and media session setup, conference policy manipulation, policy control protocol (CPCP) [7], or it may be used as an25 KB (3,844 words) - 20:20, 4 October 2020
- Respecting the privacy rights and wishes of users engaged in a call For an active Recording Session, privacy or security reasons may29 KB (4,181 words) - 09:58, 1 October 2020
- must be tuned for privacy. In particular, note that both URL schemes There are two ways to perform privacy tuning on a BEEP session,18 KB (2,589 words) - 03:53, 4 October 2020
- o a single privacy protocol and associated parameters by o Its partyPrivProtocol component is called the privacy87 KB (10,290 words) - 23:18, 16 October 2020
- when identifying which policy to apply for a host are encountered. Best Current Practices on protecting privacy [BCP160] [BCP188].51 KB (6,520 words) - 11:14, 2 October 2020
- server may return it or not, based on its local policy -- as is the == Security and Privacy Considerations ==22 KB (2,934 words) - 05:04, 22 October 2020
- DNS Privacy Considerations This document describes the privacy issues associated with the use of37 KB (5,426 words) - 11:21, 2 October 2020
- Privacy Key Management Version 1 (PKMv1) Protocol Support support for IEEE 802.16 Privacy Key Management Version 1.22 KB (3,240 words) - 14:36, 21 October 2020
- The Domain Name System (DNS) does not make policy decisions about considered open to the public -- which is a cause for some privacy9 KB (1,250 words) - 21:24, 5 October 2020
- as the operation affords no privacy or integrity protect itself. oldPasswd is not present, the server MAY use other policy to10 KB (1,473 words) - 18:50, 3 October 2020
- data - e.g., using digital signatures - and privacy is obtained by establish, in advance, a security policy that decides:25 KB (3,789 words) - 00:26, 20 October 2020
- Report from the Internet Privacy Workshop On December 8-9, 2010, the IAB co-hosted an Internet privacy workshop47 KB (6,885 words) - 12:24, 1 October 2020
- authentication, are policy decisions at the discretion of the below. Application of additional restrictions and policy are at the22 KB (3,039 words) - 09:19, 2 October 2020
- and privacy policies over the Internet. Location information is a GEOPRIV focuses on the privacy and security issues, from both a14 KB (2,062 words) - 14:37, 4 October 2020
- implementations of Distributed Routing Policy System [3]. An initial + Version: PGP for Personal Privacy 5.010 KB (1,276 words) - 03:31, 20 October 2020
- Samuelson Law, Technology & Public Policy Clinic at the same time protect the privacy of the individuals involved.57 KB (8,127 words) - 07:04, 4 October 2020
- authorization policy.) many of the same privacy consideration and arguments that apply to12 KB (1,335 words) - 23:14, 16 October 2020
- privacy are not required to operate or implement the header field. of lack of support of this HTTP extension or because of a policy29 KB (4,236 words) - 03:46, 2 October 2020
- supported types of client authentication, are policy decisions at the criteria below. Application of additional restrictions and policy28 KB (3,765 words) - 09:17, 2 October 2020
- o Create a mailing list for discussion with a policy of open access. [[RFC1421|RFC 1421]] (Privacy Enhancement for Internet Electronic Mail: Part I:22 KB (2,981 words) - 21:43, 4 October 2020
- declares a policy, communicated from the server to the client future by the Frame-Options directive in the Content Security Policy22 KB (3,146 words) - 23:42, 1 October 2020
- Mobile IPv6 Location Privacy Solutions IPv6 location privacy problem described in [[RFC4882|RFC 4882]], and propose97 KB (14,578 words) - 19:09, 13 October 2020
- - Policy constraints may dictate that the location provided remains | Policy * |27 KB (3,914 words) - 16:07, 14 October 2020
- Security and Privacy Considerations for This document discusses privacy and security considerations for37 KB (4,930 words) - 13:14, 2 October 2020
- An Architecture for Location and Location Privacy time protect the privacy of the individuals involved. This document85 KB (12,866 words) - 08:49, 1 October 2020
- [P3P] Marchiori, M., Ed., "The Platform for Privacy Preferences Another browser-based issue comes about when the Platform for Privacy14 KB (2,002 words) - 14:46, 1 October 2020
- Considerations section but the security and privacy aspects are best Common Policy [[RFC4745]], Geolocation Policy [GEO-POLICY], or more30 KB (3,930 words) - 12:02, 1 October 2020
- Common Open Policy Service (COPS) secure Common Open Policy Service (COPS) connections over the23 KB (3,482 words) - 18:04, 4 October 2020
- authentication, authorization, access control, and privacy policies. === Authentication and Privacy ===38 KB (5,856 words) - 11:51, 19 October 2020
- administrators to provide policy that can override the default These addresses may also be "preferred" or "deprecated" [2]. Privacy46 KB (6,748 words) - 03:02, 4 October 2020
- === History-Info with Privacy Header Field === This is an example of the use of the Privacy header field with a77 KB (9,664 words) - 01:35, 2 October 2020
- 5) Acts as a technical policy liaison and representative for the set technical development priorities, to discuss policy matters which23 KB (3,230 words) - 15:45, 15 October 2020
- data consumer or provider consent. If content privacy is a concern, operator and its privacy policy. Those documents may be31 KB (4,351 words) - 11:20, 4 October 2020
- liaison to the Office of Science and Technology Policy (headed by the and technology policy affecting the Internet. It endorses and25 KB (3,510 words) - 13:49, 16 October 2020
- message to carry Device identifiers. Privacy and security The usage of identifiers in HELD introduces a new set of privacy49 KB (6,992 words) - 04:19, 22 October 2020
- does not specify a standard, or a policy of the IAB. Distribution of issues like violation of privacy, break-in attempts or10 KB (1,559 words) - 13:51, 16 October 2020
- This registry uses the "Specification Required" policy described in Note that the "Specification Required" policy implies review by a16 KB (2,279 words) - 07:53, 2 October 2020
- specification defines a value for the Privacy header field that 14.2. Registration of "history" for SIP Privacy Header Field . 2772 KB (10,588 words) - 23:53, 1 October 2020
- Policy-Based Routing Database 1479 Steenstrup Jul 93 Inter-Domain Policy Routing Protocol36 KB (4,738 words) - 08:52, 18 October 2020
- information under several privacy and integrity modes. several privacy and integrity modes. The most secure of the privacy49 KB (6,879 words) - 04:50, 2 October 2020
- The distribution of location information is a privacy-sensitive task. Dealing with mechanisms to preserve the user's privacy is important102 KB (12,369 words) - 21:21, 11 October 2020
- Common Policy: A Document Format for Expressing Privacy Preferences aspects. An XML schema specifies the language in which common policy52 KB (7,283 words) - 15:55, 5 October 2020
- Category: Informational Samuelson Law, Technology & Public Policy Clinic and navigation capabilities gives rise to significant privacy and36 KB (5,612 words) - 07:06, 4 October 2020
- known as policy based management. ask their Policy Server for an admit/reject decision for a particular20 KB (2,572 words) - 20:20, 3 October 2020
- o An OPES System MUST include information about its privacy policy, enforcing the policy.28 KB (4,353 words) - 11:01, 4 October 2020
- == Encryption Policy == === Encryption Policy Specification ===17 KB (2,458 words) - 18:41, 1 October 2020
- solution to configure each host's policy table by hand. So, for such Host, and using the corresponding static address selection policy28 KB (3,363 words) - 13:44, 11 October 2020
- communicating privacy-sensitive presence information and which has preferences. Privacy lapses may result from poor protocol security45 KB (5,842 words) - 15:21, 4 October 2020
- Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information72 KB (9,680 words) - 18:26, 1 October 2020
- 8. Privacy Considerations policy for the use of ITS certificates, including a specification of28 KB (3,549 words) - 06:57, 25 October 2020
- Proxies commonly apply policy to the presence of certain SIP header to remove UUI header fields in a request or response based on policy.39 KB (5,731 words) - 07:32, 2 October 2020
- provided" defined in [[RFC7315|RFC 7315]]. Based on operator policy and/or documented in [[RFC7315]], P-Access-Network-Info may include privacy14 KB (2,040 words) - 07:11, 3 October 2020
- authentication, are policy decisions at the discretion of the More information about anonymity, pseudonymity, and privacy37 KB (5,044 words) - 09:16, 2 October 2020
- months. The mapping information is highly privacy sensitive; if extent, such a policy will minimize the probability that all ports in19 KB (2,972 words) - 14:07, 2 October 2020
- Organizations that have implemented a security policy can issue policy, the clearance levels held by the subject, and additional32 KB (4,493 words) - 14:45, 21 October 2020
- authentication protocol and a single privacy protocol. It is to define one such authentication and one such privacy95 KB (11,638 words) - 23:18, 16 October 2020
- a session peering policy, provided in an informative appendix. It service provider policy parameters. These are some of the reasons47 KB (6,640 words) - 08:39, 1 October 2020
- contains a sequence of policy information terms that identify upon. This value suggests a policy value to be used in the28 KB (3,527 words) - 21:32, 5 October 2020
- the privacy level achieved. Ascertaining the TLS connection's privacy privacy is not high enough for it to continue, it SHOULD gracefully21 KB (3,169 words) - 15:12, 3 October 2020
- Resolution does not define Geographic Privacy policy. LaRes does not define Geographic Privacy policy.26 KB (3,963 words) - 09:36, 4 October 2020
- evolvability, usability, and security and privacy. An RDS that is an expense beyond reason. In addition there may be policy as well as56 KB (8,781 words) - 18:39, 19 October 2020
- Privacy Extensions for Stateless Address Autoconfiguration in IPv6 regularly in such environments would be desirable to lessen privacy38 KB (5,754 words) - 18:26, 3 October 2020
- administrators to provide policy that can override the default Privacy considerations have introduced the concepts of "public63 KB (8,899 words) - 17:27, 1 October 2020
- 2.5. Access Policy 6 === Access Policy ===67 KB (7,383 words) - 18:24, 19 October 2020
- single privacy protocol. The privacy protocol provides a mechanism by protected from disclosure. The privacy protocol in this memo81 KB (11,577 words) - 14:13, 16 October 2020
- must be tuned for privacy. In particular, note that both URL schemes There are two ways to perform privacy tuning on a BEEP session,21 KB (2,962 words) - 23:10, 3 October 2020
- 2.5. Access Policy 6 === Access Policy ===68 KB (7,415 words) - 18:38, 19 October 2020
- Section 3 discusses privacy issues common to all proposed solutions. It is out of scope of this document to elaborate on privacy issues44 KB (6,572 words) - 22:23, 1 October 2020
- A User Agent Profile Data Set for Media Policy SIP sessions: the Media Policy Data Set Format (MPDF). This format72 KB (9,320 words) - 18:52, 1 October 2020
- The Domain Name System (DNS) does not make policy decisions about considered open to the public -- which is a cause for some privacy12 KB (1,611 words) - 16:33, 11 October 2020
- For any application that requires privacy, the 40-bit ciphersuites adequate privacy assurance. If TLS is used to provide privacy for31 KB (4,884 words) - 21:33, 3 October 2020
- User agreements are a form of acceptable use policy (AUP) are an an policy in the form of an agreement or contract specifying terms41 KB (6,176 words) - 22:18, 29 September 2020
- may also choose to use randomly generated addresses for privacy IPv6 introduces the concept of privacy addresses [PRIVADDR]. These40 KB (5,747 words) - 23:40, 3 October 2020
- The actual charter text represents a policy enjoined and enforced by [[[RFC1421|RFC 1421]]] Linn, J., "Privacy Enhancement for Internet Electronic17 KB (2,601 words) - 19:22, 19 October 2020
- authentication, authorization, access control, and privacy policies. policy.82 KB (11,723 words) - 11:52, 19 October 2020
- To help assure healthcare privacy and security in automated systems, [E2147], and the Joint NEMA/COCIR/JIRA Security and Privacy Committee71 KB (9,145 words) - 10:43, 4 October 2020
- policy. Understanding the various scenarios and users of measuring privacy issues. These are summarized in Section 7 and considered in35 KB (5,111 words) - 09:33, 2 October 2020
- policy that controls which servers the client will establish LDAP establish LDAP sessions that are inconsistent with this policy. If a26 KB (3,688 words) - 11:31, 5 October 2020
- PU and PE B. This will violate security policy. For example, if the the pool). If the "choose a member at random" policy is employed,31 KB (4,535 words) - 17:01, 11 October 2020
- Privacy Considerations for Internet Protocols This document offers guidance for developing privacy considerations76 KB (10,934 words) - 22:29, 1 October 2020
- Privacy Example Application: TV broadcast, sender policy defines43 KB (5,217 words) - 03:04, 20 October 2020
- policy in this respect will need to be reflected in the above Privacy issues have been raised regarding the unwarranted disclosure17 KB (2,474 words) - 20:18, 11 October 2020
- Public Policy Program of the John F. Kennedy School of Government, 1174 Cerf Aug 90 IAB Recommended Policy on Distributing42 KB (5,801 words) - 13:54, 16 October 2020
- privacy concerns. include attack vectors or system descriptions used in a privacy-16 KB (2,169 words) - 08:47, 2 October 2020
- 2.11 RFC3041 - Privacy Extensions for Address Configuration specifications. The use of privacy addresses [RFC-3041] for site-40 KB (5,880 words) - 23:42, 3 October 2020
- 7.1. Privacy Considerations === Privacy Considerations ===26 KB (3,297 words) - 11:37, 30 October 2020
- furthermore, Proxy-B has a policy that requires the client's SIP connection based on its policy.14 KB (1,913 words) - 14:57, 21 October 2020
- on local policy. However, based on local policy, a UAC MAY include an access token33 KB (4,313 words) - 11:23, 30 October 2020
- 1.5.3. Person Determining CPS Suitability for the Policy ..12 This document has been generated to complement the Certificate Policy58 KB (8,126 words) - 06:35, 2 October 2020
- Policy, provisioning, and processing of authentication and (command syntax, terms of service, privacy policy, rate-limiting36 KB (5,268 words) - 08:32, 2 October 2020
- ==== Registration Policy ==== The Registration Policy for 'geo' URI Parameters and their value37 KB (5,332 words) - 20:25, 15 October 2020
- 5. Privacy Considerations for any policy decisions. Integrity protection prevents an adversary28 KB (3,871 words) - 10:54, 30 October 2020
- Privacy Enhancement for Internet Electronic Mail: This memo is the outgrowth of a series of meetings of the Privacy and76 KB (11,771 words) - 23:15, 16 October 2020
- authentication and privacy. * Negotiation discloses information and therefore raises privacy14 KB (1,944 words) - 15:47, 4 October 2020
- === Clear Security and Privacy Considerations === security and privacy implications for systems that use the scheme;36 KB (5,174 words) - 10:45, 2 October 2020
- DNS cache or DNS policy to resolve address queries from hosts. namely, source address selection policy, next hop41 KB (5,620 words) - 02:10, 2 October 2020
- it is important that policy is applied on these names consistently. o IdPs SHOULD apply policy based on the RP's identity associated53 KB (7,107 words) - 18:53, 2 October 2020
- authentication, authorization, and policy functions. The RADIUS retrieve the mobile node's policy profile and for performing service62 KB (9,602 words) - 14:32, 1 October 2020
- required and the parameters to be used, discusses some of the policy 'C' - Clear - neither Integrity nor Privacy50 KB (6,910 words) - 17:14, 4 October 2020
- on local policy. A server MAY treat a ticket as valid for a shorter unspecified, a client has its own local policy that determines when29 KB (3,872 words) - 11:21, 5 October 2020
- a separate policy table (like "/etc/sudoers") is consulted to if the UAS is unwilling (perhaps due to policy) to answer in the mode50 KB (7,495 words) - 17:22, 11 October 2020
- for any policy decisions. Integrity protection prevents an adversary == Privacy Considerations ==28 KB (3,765 words) - 16:01, 2 October 2020
- security policy this will thwart MitM attacks against inner methods. helps to maintain peer privacy.44 KB (6,202 words) - 16:34, 1 October 2020
- (invoke labeled policy) distinction. regulatory policy and local administrative procedures). A gateway33 KB (4,848 words) - 03:06, 4 October 2020
- Location Privacy in Internet Applications" [[RFC6280]], Section 7. The Target is the entity whose privacy the architecture described in65 KB (9,257 words) - 06:26, 2 October 2020
- This memo describes the design, deployment, and privacy option's privacy considerations in considerable detail and highlights41 KB (6,204 words) - 07:00, 3 October 2020
- The privacy level that is achieved using 3pcc is high, since the To achieve a higher degree of privacy, endpoints following the 3pcc17 KB (2,389 words) - 17:17, 11 October 2020
- elements to ensure compliance with corporate policy. centralized orchestration infrastructures, imperative policy31 KB (4,517 words) - 02:35, 3 October 2020
- privacy, security, flexibility, reachability) that are sometimes in Internet policy, they rarely can participate broadly, nor are they21 KB (3,172 words) - 11:31, 30 October 2020
- particular for Privacy Enhanced mail [Lin89]. useful for an even wider range of applications (e.g., policy based42 KB (6,047 words) - 23:16, 16 October 2020
- origin policy as well as the "nuts and bolts" of comparing and of the same-origin policy, the details of which are left to other34 KB (4,946 words) - 12:10, 1 October 2020
- cases. Security policy negotiation, including authentication and authorization to define the per-subscriber policy at the policy/AAA33 KB (4,791 words) - 19:06, 13 October 2020
- Privacy Extensions for Stateless Address Autoconfiguration in IPv6 desirable to lessen privacy concerns, it should be noted that the48 KB (7,253 words) - 19:43, 5 October 2020
- privacy. the NETCONF program when strong user authentication or data privacy32 KB (4,558 words) - 15:53, 5 October 2020
- make policy decisions based on the attributes of a participant in a authorization, as well as allows greater privacy for users of an32 KB (4,620 words) - 10:55, 5 October 2020
- privacy, and protection against related-protocol attacks. the hash extension and to enhance privacy by adding randomness to44 KB (6,636 words) - 12:33, 4 October 2020
- the functional requirements for robustness, security, and privacy if so desired, and if allowed by Service Provider policy.24 KB (3,503 words) - 17:04, 4 October 2020
- As networks scale and policy becomes an increasingly important part and coherent control over policy and control-plane state, but it also29 KB (4,338 words) - 02:29, 3 October 2020
- offering privacy for a user who requests and uses an X.509 personal privacy, and thus there are increasing demands for privacy-60 KB (8,765 words) - 22:24, 11 October 2020
- for compliance with [[RFC2119|RFC 2119]] [3] do not reference or specify policy that facilitates and implements global addressing policy based on the41 KB (5,961 words) - 07:20, 4 October 2020
- ==== Data Privacy ==== Data privacy, while desirable, is not as important in all44 KB (6,825 words) - 01:05, 20 October 2020
- or that raise significant privacy concerns MUST be explicitly listed by name and the reasons for the sensitivity/privacy40 KB (5,877 words) - 03:03, 22 October 2020
- ENC (Privacy Protected Command). Policy is not specified by this document. In particular, client and51 KB (7,419 words) - 17:45, 19 October 2020
- state and status to the protocol. The general policy is to gain The mail Privacy procedures [RFC-1113, RFC-1114, and RFC-1115] are29 KB (3,688 words) - 15:46, 15 October 2020
- A human user who established policy for and configures the print A human user who carries out the policy established by the33 KB (4,808 words) - 13:01, 4 October 2020
- and filtering techniques. (A signing policy can provide additional o Privacy Enhanced Mail (PEM) was first published in 1987 [[RFC0989]].45 KB (6,437 words) - 21:27, 11 October 2020
- also help address privacy-related concerns, along with the regulatory the obvious implications for security and privacy, or else be28 KB (4,023 words) - 18:48, 2 October 2020
- interactive query or through accessing configured policy). If requests ahead of time by providing policy to the user agent. This39 KB (5,589 words) - 03:37, 4 October 2020
- privacy shortcomings, a revision will be worked through the IETF for == Privacy Note ==57 KB (8,538 words) - 22:11, 2 October 2020
- you should obtain the security policy of the site that you intend to use as your access provider, and read it. A security policy is a62 KB (10,173 words) - 22:53, 19 October 2020
- implies the default subscription filtering policy. The default policy is as follows:78 KB (10,632 words) - 12:37, 5 October 2020
- This implies the default subscription filtering policy. The default policy is:69 KB (9,385 words) - 17:35, 4 October 2020
- policy and selects one or more Redirection Targets (RTs) and policy, possibly falling back to querying an alternative dCDN(s) if64 KB (8,140 words) - 07:06, 3 October 2020
- server's proxy authorization policy. confidential information that requires privacy protection.9 KB (1,342 words) - 20:14, 4 October 2020
- this document and are a matter for local or network-wide policy. The IS-IS provides no encryption mechanism for protecting the privacy of28 KB (4,254 words) - 22:37, 5 October 2020
- policy about which servers to connect to using which security with this policy.18 KB (2,699 words) - 18:13, 19 October 2020
- implement behavior that is equivalent to a "privacy service" (as described in [2]) performing both Header Privacy and Session50 KB (7,163 words) - 20:23, 15 October 2020
- topic of IPv6 address allocation policy. This memo addresses the However, in general, we observe that technical delegation policy can20 KB (3,102 words) - 21:02, 3 October 2020
- privacy and integrity protected) data object that can be used by a At a minimum, all supported credential formats SHOULD provide privacy42 KB (5,901 words) - 08:24, 4 October 2020
- signature. A secure mailing list agent may change the receipt policy element, a Mail List receipt policy has not been specified114 KB (16,011 words) - 01:19, 20 October 2020
- constitute a privacy leak. application will have to apply local policy. For privacy reasons, an37 KB (5,606 words) - 03:06, 3 October 2020
- It MAY delete the ticket earlier based on local policy. A server MAY unspecified, a client has its own local policy that determines when35 KB (4,754 words) - 22:23, 5 October 2020
- depends on the policy configured by the administrator. failure. This depends on the administrative policy in place.38 KB (5,678 words) - 02:25, 2 October 2020
- will check configuration and policy to determine if the attributes This document uses identity management and privacy terminology from97 KB (14,337 words) - 18:42, 2 October 2020
- Labeled NFS (see Section 9 of [[RFC7862]]) uses an MLS policy with to server-side policy. See [[RFC7862]].45 KB (6,545 words) - 21:19, 2 October 2020
- made by the IETF will comply with the IETF IPR policy as documented IETF participants, under the IETF's IPR policy, as documented in RFC15 KB (2,232 words) - 12:36, 4 October 2020
- traffic, security and privacy, and operations and network variations depending on economic, technical and public policy33 KB (4,948 words) - 22:07, 29 September 2020
- security policy database, which specifies that a certain security security policy database according to a dynamically assigned home42 KB (6,229 words) - 13:54, 5 October 2020
- As far as security and privacy are concerned, this document considers fulfill the goals of a security policy. On the one hand, NAT does82 KB (12,384 words) - 18:13, 5 October 2020
- authorized by the Printer's administrator-configured security policy Furthermore, the Printer's security policy MAY limit the attributes61 KB (7,905 words) - 13:00, 4 October 2020
- illustrates examples of Security Policy Database and Security required Security Policy Database (SPD) and Security Association48 KB (7,351 words) - 18:31, 5 October 2020
- client according to local policy before password-based authentication authenticated by the server according to local policy to ensure that14 KB (2,126 words) - 15:52, 5 October 2020
- Section 9 also specifies optional use of the Privacy header in indicator, which can indicate that privacy is required (presentation125 KB (16,682 words) - 11:10, 5 October 2020
- decisions on a system-wide policy established by an administrator or Policy Identifier (PI): an optional part of the definition of a32 KB (5,028 words) - 03:02, 2 October 2020
- trusted third parties. This is a trust policy and/or reproduction, and ensure privacy.25 KB (3,610 words) - 03:27, 4 October 2020
- ==== Privacy Labels ==== because policy does not allow it to be given under the current72 KB (7,469 words) - 21:03, 4 October 2020
- monitoring or enforcing compliance to an organization's policy. document discusses some potential security and privacy considerations111 KB (16,582 words) - 13:32, 11 October 2020
- IPv6 Privacy Extension [PRIVACYTEXT]. or Mobile IP privacy extensions, without requiring them to update27 KB (4,098 words) - 17:49, 5 October 2020
- o It allows for policy-based comparisons of network properties, achieves a policy-defined consistency, rather than bitwise68 KB (10,105 words) - 16:33, 1 October 2020
- o How to bind traffic to a given SF chain is policy-based. against policy for subsequent application of the required set of63 KB (9,060 words) - 12:06, 2 October 2020
- Pinning Policy applies to this Pinned Host as well as any subdomains remove its cached Pinning Policy information (including the51 KB (7,724 words) - 08:13, 2 October 2020
- provider's network planning policy, etc. protection requirements (including privacy protection requirements).41 KB (5,432 words) - 04:56, 2 October 2020
- policy issued by the authorities in charge of ENUM administration. act(s) as NAE for ported numbers depends on local policy.27 KB (3,294 words) - 15:33, 5 October 2020
- ==== Privacy Protocol 8 ==== ==== User-based Security Model Primitives for Privacy 11 ====146 KB (19,127 words) - 18:23, 19 October 2020
- The table is managed by IANA, following the allocation policy coordinate and align their respective policy expressions.48 KB (5,927 words) - 03:01, 2 October 2020
- ==== Privacy Protocol 8 ==== ==== User-based Security Model Primitives for Privacy 11 ====146 KB (19,159 words) - 18:37, 19 October 2020
- packets in a flow to assist firewalls and NATs in policy decision and and issues of preserving end-user privacy. While some discussion26 KB (3,625 words) - 12:04, 2 October 2020
- === Registration Policy and Expert Guidance === The "CAtypes" registry is altered to operate on a registration policy33 KB (4,707 words) - 19:50, 1 October 2020
- The reason for this policy is that the UDP service may be used to furthermore such a policy would provide no feedback to the sender of16 KB (2,284 words) - 14:08, 16 October 2020
- privacy into account. Many applications of speech technology deal statement accompanying the protocol specification(s). Privacy37 KB (5,251 words) - 19:06, 4 October 2020
- Addresses [HBA] and privacy addresses [[RFC4941]]. allowed by the security policy.56 KB (8,007 words) - 19:11, 13 October 2020
- any local policy requirements (which are not discussed here or in === False Privacy ===25 KB (3,927 words) - 13:52, 1 October 2020
- access network to which they are attached. Policy systems in mobility architectures, such as Policy and Charging Control (PCC)35 KB (4,596 words) - 19:24, 2 October 2020
- expiration policy and are no longer accessible by the end user. Information about which server expiration policy was applied may29 KB (4,239 words) - 18:18, 11 October 2020
- to an appropriate policy once that buffer has been exceeded. Also, used for privacy reasons (see Section 8.5). If the user's identity67 KB (7,557 words) - 14:29, 4 October 2020
- o Avoid the Security Policy Issue Security policy may forbid a Mobile Router from tunneling traffic81 KB (12,099 words) - 18:45, 5 October 2020
- ==== Privacy Labels ==== because policy does not allow it to be given at the current level73 KB (7,823 words) - 12:44, 4 October 2020
- to the client (depending on policy). The DHCPOFFER message is clients. The reservation policy SHOULD be configurable.27 KB (3,907 words) - 11:12, 2 October 2020
- of privacy, security, and end-to-end data integrity. Clark, et al. policy of no commercial use. The major stakeholders in the Internet32 KB (4,886 words) - 07:39, 4 October 2020
- definitions, although it does mention some basic policy areas This exchange is masked for party privacy protection using a127 KB (17,813 words) - 23:12, 19 October 2020
- levels on networks. Policy guidelines for handling incidents are Security and privacy considerations are of high concern since146 KB (20,694 words) - 02:19, 22 October 2020
- Appropriate access control, privacy, and accounting mechanisms must and the networks themselves, privacy of user data, and accounting54 KB (7,390 words) - 01:16, 12 October 2020
- or GETDEVICEINFO operations via RPCSEC_GSS with the privacy service or GETDEVICEINFO operations with RPCSEC_GSS with the privacy64 KB (9,951 words) - 01:20, 12 October 2020
- must be tuned for privacy. In particular, note that both URL schemes There are two ways to perform privacy tuning on a BEEP session,31 KB (4,351 words) - 17:26, 4 October 2020
- and apply authorization policy before allowing the participant to Assuming that all security and policy requirements have been met, a82 KB (8,463 words) - 12:46, 5 October 2020
- associating a given user with the access control policy (known as a how the policy associated with a given role is put in place.33 KB (4,284 words) - 02:40, 22 October 2020
- do this is to protect the user's privacy. In such cases, the GRUU This would mean that the policy of the domain is that requests can81 KB (12,722 words) - 22:14, 11 October 2020
- report an error is based on policy. might carry privacy sensitive information. It is therefore25 KB (3,672 words) - 19:45, 2 October 2020
- policy. The same or different preferences may be used for each OSPF provides no encryption mechanism for protecting the privacy of34 KB (5,235 words) - 22:36, 5 October 2020
- interactions. Within BEEP, features such as authentication, privacy, if the privacy or authentication that has been negotiated is49 KB (7,086 words) - 21:22, 3 October 2020
- Secure HTTP message. All except 'Content-Type' and 'Content-Privacy- ==== Content-Privacy-Domain ====79 KB (11,161 words) - 01:47, 20 October 2020
- Privacy Considerations. URL string that points to a human-readable privacy policy document74 KB (10,656 words) - 10:40, 2 October 2020
- authorization per its local policy. See section 3.1.6.3. reveal authorization policy in an undesirable fashion; see section73 KB (10,639 words) - 22:44, 3 October 2020
- user of the Device, the same level of privacy protection demanded by necessary to ensure the accuracy, privacy, and confidentiality of the72 KB (10,447 words) - 01:11, 22 October 2020
- validation done by the network based on observed traffic and policy. BGP: The Border Gateway Protocol, used to manage routing policy52 KB (7,946 words) - 22:14, 1 October 2020
- community discussion and consensus, leaving policy and operational access. When this problem is addressed through proper privacy and17 KB (2,530 words) - 09:34, 18 October 2020
- privacy are obtained by using Cryptographic Message Syntax (S/MIME) specifically data privacy, data integrity/authenticity, non-49 KB (6,737 words) - 00:03, 4 October 2020
- Privacy Enhancement for Internet Electronic Mail: This document is the outgrowth of a series of meetings of the Privacy91 KB (12,594 words) - 23:15, 16 October 2020
- include fault tolerance, policy based routing, security, and time privacy and protection)20 KB (2,935 words) - 22:07, 29 September 2020
- services and violate the security policy of a system. This may be an event that violates a security policy, UAP, laws32 KB (4,705 words) - 18:55, 3 October 2020
- messages to and from anonymous participants. Privacy and supports and is willing to accept (e.g., due to local policy85 KB (12,784 words) - 12:52, 2 October 2020
- 6.3. Privacy Considerations will according to its local policy (see also Section 3.2).47 KB (5,653 words) - 10:51, 30 October 2020
- o Finally, security and privacy require careful thought. This reside? What privacy implications are caused by various design45 KB (6,291 words) - 07:54, 2 October 2020
- and privacy, the Cookie and Set-Cookie header fields are widely used privacy infelicities. For example, a server can indicate that a66 KB (9,637 words) - 08:32, 1 October 2020
- Routing Policy System Replication the basis for representing information in a routing policy system. A80 KB (11,501 words) - 03:47, 20 October 2020
- == Privacy Considerations == lease period and an assignment policy that makes the DHCP server hand35 KB (4,967 words) - 07:27, 2 October 2020
- Digital Signature Service (DSS) and Privacy Enhanced Mail (PEM) work Internet, noting a need to address privacy and data integrity issues,45 KB (6,304 words) - 12:31, 19 October 2020
- Framework Policy Information Base for Usage Feedback This document describes a portion of the Policy Information Base59 KB (6,316 words) - 04:44, 4 October 2020
- may be required as a matter of local policy. authentication and privacy mechanisms, and message formats to105 KB (11,162 words) - 18:19, 19 October 2020
- service to operate according to its own rules (for security, policy, the ability to apply specific security or policy requirements.33 KB (4,670 words) - 11:19, 1 October 2020
- may be required as a matter of local policy. authentication and privacy mechanisms, and message formats to105 KB (11,194 words) - 18:34, 19 October 2020
- policy elements for location retransmission and retention described implied policy of a SIP request that does not have a Geolocation-69 KB (9,335 words) - 11:56, 1 October 2020
- Conference Policy Server: A conference policy server is a logical function that can store and manipulate the conference policy.56 KB (6,859 words) - 19:50, 4 October 2020
- through local policy. mapping policy in the SBR, which could be realised as a simple lookup72 KB (10,744 words) - 17:54, 1 October 2020
- done in a way that respects privacy. Because the use cases for this extension are strongly tied to privacy44 KB (6,760 words) - 04:51, 2 October 2020
- | |--<conference-floor-policy>* | |--<user-admission-policy>*148 KB (15,138 words) - 13:07, 1 October 2020
- EAP-AKA includes optional identity privacy support, optional result (pseudonym) if identity privacy is in effect, as specified in163 KB (22,582 words) - 16:41, 4 October 2020
- 3084 Chan Mar 2001 COPS Usage for Policy This document describes the use of the Common Open Policy Service (COPS)44 KB (5,472 words) - 19:31, 3 October 2020
- according to a given validation policy and which contain a permanent Since the use of permanent identifiers may conflict with privacy, CAs25 KB (3,594 words) - 13:52, 4 October 2020
- 1.4.3. Privacy Protocol 8 1.6.2. User-based Security Model Primitives for Privacy 11165 KB (21,424 words) - 00:11, 20 October 2020
- authentication protocols and the use of CBC-DES as the privacy policy.161 KB (21,322 words) - 01:40, 4 October 2020
- callee's UA(s) is out of the scope of this document, as is the policy incoming dialog from its set if local policy at the callee's monitor72 KB (11,194 words) - 21:19, 1 October 2020
- A. Privacy on the advertisers. For additional information on privacy,54 KB (8,109 words) - 19:30, 3 October 2020
- maintaining privacy of communication and address space. The device ==== Privacy of Routing ====54 KB (8,128 words) - 15:29, 1 October 2020
- === Address Privacy Today === privacy.65 KB (10,343 words) - 17:15, 4 October 2020
- or a policy server. A possible optimization to minimize the delay in different EPAs, apply a composition policy, and provide39 KB (5,605 words) - 19:52, 4 October 2020
- the vendor-provided Posture Validator's policy allows for this subset local policy), so does not need to support Posture Validator163 KB (24,286 words) - 16:05, 14 October 2020
- between high-level "network-wide" policy definitions that effect policy behavior. This module is designed to integrate with the44 KB (5,080 words) - 08:09, 4 October 2020
- access control policy of RELOAD. ==== Privacy Issues ====34 KB (4,948 words) - 00:56, 3 October 2020
- 2.1.7. Address Privacy Extensions Interact with DDoS with respect to privacy in IPv6 (Appendix B).88 KB (13,333 words) - 19:44, 5 October 2020
- security properties of the same-origin policy that localStorage Because of JavaScript's same-origin policy, scripts from subdomains54 KB (8,479 words) - 08:37, 2 October 2020
- 5. Contain the policy related information, part of which may be - Generate routing tables considering local policy and25 KB (3,105 words) - 09:32, 18 October 2020
- === Policy Concerns === ==== Privacy and Regulatory Compliance ====63 KB (10,039 words) - 12:04, 1 October 2020
- GeoJSON does not provide privacy or integrity services. If sensitive data requires privacy or integrity protection, those must be provided38 KB (4,918 words) - 04:35, 3 October 2020
- network systems going down or a change in the access policy. configuration [[RFC2461]] (including privacy extensions [[RFC3041]]), and35 KB (5,101 words) - 14:09, 4 October 2020
- in the future. As policy makers debate the role of the public would represent a fundamental shift in national policy with enormous54 KB (8,274 words) - 14:02, 16 October 2020
- administrative or other policy control, as required, by setting the U equivalent to the Privacy Extensions for IPv6, generating ILNP78 KB (12,028 words) - 17:46, 1 October 2020
- PW must be processed or policy applied. It is therefore not the security and privacy requirements of the MS-PW, according to46 KB (6,281 words) - 22:54, 11 October 2020
- by Regional Internet Registry (RIR) policy and business requirements Privacy Addresses [[RFC4941]], which periodically change, rendering18 KB (2,760 words) - 01:46, 22 October 2020
- security policy can be set up so that the same method is not offered privacy-sensitive information. The channel-binding request may37 KB (4,962 words) - 23:37, 1 October 2020
- records corresponding to a telephone number, local policy can be used policy that employs some other means to select a record.31 KB (4,776 words) - 09:35, 4 October 2020
- We do not discuss PI policy here. The observations and (e.g., resilience failover, load balancing, policy-based routing, or71 KB (10,414 words) - 17:24, 11 October 2020
- [[RFC3323|RFC 3323]], A Privacy Mechanism for the Session Initiation Protocol (SIP) (S): [[RFC3323]] defines the Privacy header field, used by88 KB (11,501 words) - 18:04, 11 October 2020
- loss distributions, and privacy. whether privacy is an issue. The reason is that we expect some49 KB (6,503 words) - 13:23, 19 October 2020
- certificates to support privacy. with a different security policy. Content originators SHOULD avoid123 KB (14,507 words) - 01:06, 3 October 2020
- - A <dcp> (data collection policy) element that contains child elements used to describe the server's privacy policy for data111 KB (15,517 words) - 07:46, 4 October 2020
- on networks. Policy guidelines for handling incidents are Language (XML) documents. RID considers security, policy, and173 KB (23,916 words) - 13:56, 1 October 2020
- 3198 Westerinen Nov 2001 Terminology for Policy-Based This document is a glossary of policy-related terms. It provides42 KB (5,190 words) - 21:27, 3 October 2020
- local-policy-driven actions based on the existence (or nonexistence) administrative domain, in order to retain the user's privacy.85 KB (12,135 words) - 05:16, 2 October 2020
- policy controls in the "middle" of the network, in a so-called concerns about implementing policy controls in the "middle" of the58 KB (8,773 words) - 14:50, 1 October 2020
- 8.3. Different Privacy Issues Raised by Different Sorts of public policy development112 KB (15,573 words) - 10:43, 2 October 2020
- "Unassigned" are governed by the policy 'RFC Required' as described the policy 'First Come First Served' as described in [[RFC5226|RFC 5226]]59 KB (6,314 words) - 19:10, 1 October 2020
- request based on its strict security policy that prohibits the knows Proxy #1's security policy, which requires the inspection of22 KB (3,070 words) - 16:43, 4 October 2020
- want to erase privacy-relevant data from the logs of the automated However, John is a privacy-conscious person and is worried that Jill61 KB (9,126 words) - 13:40, 2 October 2020
- policy of the claimed sending domain to ascertain the preferred policy based on the results of the signature test.71 KB (10,886 words) - 18:19, 5 October 2020
- some additional policy details are discussed along with some initial Policy Notes22 KB (3,114 words) - 15:40, 15 October 2020
- IPsec Security Policy Database Configuration MIB security policy database of a device implementing the IPsec protocol.115 KB (13,170 words) - 17:09, 5 October 2020
- state of the presentity, for example. This is to protect the privacy Honoring of these filters is at the policy discretion of the PA.53 KB (8,054 words) - 10:15, 4 October 2020
- technical downsides related to PM in terms that policy makers settings for protocols better protect security and privacy.63 KB (9,648 words) - 12:36, 2 October 2020
- the SSH client according to local policy before password-based local policy to ensure that the incoming SSH client request is19 KB (2,733 words) - 05:56, 22 October 2020
- selection through getaddrinfo(). Privacy considerations [[RFC3041]] Mobile IPv6, IPv6 Privacy Extensions, and Cryptographically Generated45 KB (6,850 words) - 21:09, 5 October 2020
- ==== Outgoing Policy ==== may also apply an Outgoing Policy to limit the rate of port30 KB (4,485 words) - 21:17, 1 October 2020
- policy. This document specifies PT-TLS, a TLS-based Posture triggered by alerts of posture or policy changes)92 KB (13,397 words) - 20:33, 1 October 2020
- - Set the corresponding gateway or client authorization policy for scale deployment tools are desired, but local security policy80 KB (11,357 words) - 17:11, 5 October 2020
- This document also recommends a specific policy with respect to the authentication, authorization, access control, and privacy policies.14 KB (1,846 words) - 21:52, 19 October 2020
- may be required as a matter of local policy. authentication and privacy mechanisms, and message formats to115 KB (12,265 words) - 00:08, 20 October 2020
- objects defined in Section 4.3) according to policy specified on the processing times is a metric of interest. If allowed by policy, a47 KB (7,179 words) - 20:27, 15 October 2020
- | +------>| Policy | specification MUST support this policy feature on a per-MN and per-22 KB (2,904 words) - 02:09, 2 October 2020
- peer's local policy and configuration, and is outside the scope of "Proxies are frequently used to implement policy in roaming26 KB (2,965 words) - 18:33, 4 October 2020
- actually exists. If such behavior could affect admission policy the claim being asserted by the token, but may have privacy44 KB (5,407 words) - 10:55, 4 October 2020
- This document uses identity management and privacy terminology from Note: Also, the policy to which eduroam participants subscribe75 KB (10,917 words) - 10:42, 2 October 2020
- signature policy is a set of rules for the creation and validation of particular signature policy as meeting its requirements.83 KB (8,857 words) - 20:00, 3 October 2020
- o Section 6 discusses user privacy issues. security association database (SAD) and security policy database75 KB (10,891 words) - 13:48, 1 October 2020
- may be required as a matter of local policy. Models, authentication and privacy mechanisms, and message115 KB (12,392 words) - 01:36, 4 October 2020
- The policy for retrying delivery of failed notifications is specified decisions about notification text, for reasons such as privacy17 KB (2,491 words) - 12:30, 1 October 2020
- DESCRIPTION "The ID of the pool policy" "The pool policy of this pool element."72 KB (6,807 words) - 20:16, 11 October 2020
- Additional Background: Maintaining the privacy of users is This is a critical area of concern for end users, privacy47 KB (5,945 words) - 03:26, 22 October 2020
- identity to the service for privacy reasons. When policy allows, the KDC issues an anonymous ticket. If the32 KB (4,902 words) - 03:30, 22 October 2020
- transferred, privacy protections, such as IPSEC or TLS, SHOULD be in password(s). Use of policy aware clients and servers is RECOMMENDED.15 KB (2,094 words) - 19:45, 3 October 2020
- privacy of the data making up the communication. While these client based on policy determination by either AAAH or AAAL server.55 KB (7,964 words) - 17:06, 3 October 2020
- - A <dcp> (data collection policy) element that contains child elements used to describe the server's privacy policy for data112 KB (15,349 words) - 19:31, 5 October 2020
- to policy reasons. In this case, the Child publishes CDNSKEY == Privacy Considerations ==33 KB (5,136 words) - 05:48, 2 October 2020
- Policy Requirements for Time-Stamping Authorities (TSAs) This document defines requirements for a baseline time-stamp policy76 KB (11,016 words) - 05:47, 4 October 2020
- 1. To centralize the authentication and policy enforcement functions involved in the access policy enforcement portion of the IEEE 802.11147 KB (22,511 words) - 18:10, 11 October 2020
- o A <dcp> (data collection policy) element that contains child elements used to describe the server's privacy policy for data112 KB (15,180 words) - 19:09, 13 October 2020
- 1092 Rekhter Feb 89 EGP and Policy Based Routing established by a policy decision.44 KB (6,125 words) - 15:42, 15 October 2020
- Sender Policy Framework [SPF], as these are sometimes evidence of but it MAY be set to "other" for local policy reasons.26 KB (3,453 words) - 14:53, 1 October 2020
- Appendix A. Privacy Considerations policies to meet their needs without compromising general privacy73 KB (7,850 words) - 15:03, 5 October 2020
- one or several parts of this infrastructure for policy reasons (i.e., [[RFC3041]] privacy extension or cryptographically generated addresses41 KB (5,743 words) - 19:25, 5 October 2020
- policy at the client will determine whether or not to continue the policy) when generating OTP values with a newly89 KB (12,282 words) - 16:10, 5 October 2020
- example, to protect end-users' privacy when communicating CDNI compatible with privacy protection, to access some CDNI Logging118 KB (16,887 words) - 03:48, 3 October 2020
- The PGP type indicates a Pretty Good Privacy certificate as described trusted key and this conforms with the user's security policy.17 KB (2,440 words) - 23:29, 19 October 2020
- 2.5. Access Policy 6 === Access Policy ===69 KB (7,656 words) - 00:13, 20 October 2020
- local policy. For example, in the United States, a dial string SIP security, privacy, and encryption. The SF of an SBE can also29 KB (4,097 words) - 11:15, 1 October 2020
- typically filtered based on elapsed time and local policy. Problems advertise and which to omit is a local policy matter, and may be35 KB (5,239 words) - 16:42, 5 October 2020
- publication of a set of policy recommendations which came out of a as necessary to prevent the circumvention of national privacy laws by28 KB (4,251 words) - 11:11, 27 October 2014
- policy based decision, often based upon proximity, but may be based Common policy per organization possible but still requires initial50 KB (6,707 words) - 18:25, 3 October 2020
- to distribute it. There are specific privacy considerations relating privacy and security challenges. These are described in more detail127 KB (17,470 words) - 01:07, 2 October 2020
- Other extensions MAY be added according to local policy. the requirements of local policy and [[RFC4120]], Sections 1.2 and24 KB (3,467 words) - 17:19, 1 October 2020
- B) User Address Space privacy. Current IPv4 network addressing resources and the corporate need for privacy. "Local addresses"30 KB (4,400 words) - 07:49, 19 October 2020
- policy of the proxy server permits her to use. It then computes a scheme, the policy of the authentication service determines whether90 KB (13,937 words) - 10:39, 5 October 2020
- deploying their own CDNs. Subject to the policy of the Content limits and policy. This information can be taken into account47 KB (6,273 words) - 05:40, 2 October 2020
- preexisting relationship and privacy issues are addressed within the information are subject to privacy constraints. These constraints200 KB (23,941 words) - 20:32, 2 October 2020
- privacy addresses [13]. policy and for picking one Home Agent. If the Home Agent of choice53 KB (8,031 words) - 21:22, 5 October 2020
- Inter-Domain Policy Routing Protocol Specification: Version 1 Inter-Domain Policy Routing (IDPR). IDPR includes the virtual235 KB (34,670 words) - 23:22, 16 October 2020
- The SPRING architecture MUST allow putting the policy state in the Hence, the policy is instantiated in the packet header and does not32 KB (4,365 words) - 20:48, 2 October 2020
- referred to as privacy. (Note: some literature from the security * privacy: confidentiality;52 KB (7,236 words) - 01:35, 4 October 2020
- privacy: The <privacy> element distinguishes whether the | <privacy> | x | x | x | x | |61 KB (8,074 words) - 10:51, 5 October 2020
- Ticket Policy: Policy for ticket generation and resolution, PET: Privacy Enhancing Technologies118 KB (17,596 words) - 02:17, 22 October 2020
- === Access Policy === an access control policy for a group of principals.69 KB (7,724 words) - 01:41, 4 October 2020
- IANA action. The policy for adding top-level service labels is 'sos' and 'counseling'.) The policy for assigning labels to sub-28 KB (3,972 words) - 21:28, 5 October 2020
- policy, routing/signaling protocols, etc.) details of the associated policy is discussed in Section 7.8. The85 KB (12,910 words) - 02:24, 3 October 2020
- services, a return/receipt facility, and support for privacy and sites. Develop a cooperative effort on authentication and privacy66 KB (9,363 words) - 13:55, 16 October 2020
- == Scenarios for Media Policy Control == The contents of each sub-window can be defined by a conference policy32 KB (4,924 words) - 13:06, 5 October 2020
- retrieve the associated authentication policy. Alternatively, an to an appropriate policy once that buffer has been exceeded. Also,89 KB (11,780 words) - 04:53, 4 October 2020
- asserts its belief that this policy described herein is an accurate endorsement or recommendation of this policy by the IESG. The IESG24 KB (3,509 words) - 14:28, 19 October 2020
- grouped under a common administrative policy for routing. local policy, uses these to route the request to a destination34 KB (5,186 words) - 19:02, 5 October 2020
- able to obtain the client's identity (perhaps due to privacy concerns local security policy.161 KB (21,919 words) - 15:20, 3 October 2020
- authenticated email. DMARC is a mechanism for policy distribution The Sender Policy Framework ([SPF]) and DomainKeys Identified Mail137 KB (19,958 words) - 22:15, 24 October 2020
- This document also recommends a specific policy with respect to the authentication, authorization, access control, and privacy policies.16 KB (2,165 words) - 21:50, 19 October 2020
- filtering and application of policy. This approach is used today in policy, but there is no requirement that an intermediary element be22 KB (3,104 words) - 14:26, 1 October 2020
- cost, user preference, and policy. How to select the target BS is When the MN decides to change links based on its policy such as the36 KB (5,003 words) - 14:40, 11 October 2020
- realization of this framework requires a policy infrastructure. The limitations of other data elements. Additional policy considerations127 KB (14,939 words) - 14:06, 11 October 2020
- administrative policy MAY mandate the inclusion of the policy to use the priority levels indicated. If the request is65 KB (8,991 words) - 21:01, 4 October 2020
- process about policy on the network side will be enriched with one of those buckets, and according to the configured policy, his/20 KB (2,889 words) - 14:06, 2 October 2020
- visibility into the lower-layer network). VNTM uses local policy and necessary and acceptable within VNTM's policy constraints.68 KB (9,938 words) - 22:09, 11 October 2020
- Use of identifiers such as IMEI could have privacy implications, the Specification Required policy [[RFC5226]].32 KB (4,560 words) - 08:00, 2 October 2020
- EAP-SIM specifies optional support for protecting the privacy of (IMSI) or a temporary identity (pseudonym) if identity privacy is in186 KB (26,232 words) - 16:40, 4 October 2020
- Certificate Policy and Certification Practices Framework certificate policy definition or a certification practice statement.79 KB (10,750 words) - 23:18, 19 October 2020
- and provides the policy and keying material to members of a secure insertion of keys and policy into the relevant databases.50 KB (6,901 words) - 19:01, 11 October 2020
- send the I1 packets can be decided based on local policy. For === Privacy Considerations ===67 KB (9,918 words) - 16:02, 14 October 2020
- 1981 by DARPA to become the general technical and policy oversight destination, to permit variation in TOS and policy conformance.51 KB (7,064 words) - 14:05, 16 October 2020
- and control parameters to a host such that a flow policy can be == Gateway Flow Policy and State ==96 KB (14,354 words) - 19:35, 3 October 2020
- utilize IPsec to provide for tunnel authentication, privacy L2TP to tie IPsec filters and policy to the same peer.54 KB (8,210 words) - 21:20, 3 October 2020
- POLICY REQUIREMENTS FOR INTER ADMINISTRATIVE DOMAIN ROUTING document articulates the requirements for policy based routing and48 KB (7,376 words) - 15:45, 15 October 2020
- An Architecture for Inter-Domain Policy Routing We present an architecture for inter-domain policy routing (IDPR).77 KB (11,886 words) - 23:22, 16 October 2020
- 989 Linn Feb 87 Privacy Enhancement for Internet outgrowth of a series of IAB Privacy Task Force meetings and of internal55 KB (7,847 words) - 11:37, 27 October 2014
- privacy -- and support topological changes at a high rate. Ideally, based on policy.15 KB (2,065 words) - 05:35, 22 October 2020
- DNS does not make policy decisions about the records that it shares which is a cause for some privacy considerations.15 KB (2,209 words) - 08:28, 4 October 2020
- this information is provided in-band, the privacy, performance, and explicit security policy, application protocol specification, or17 KB (2,410 words) - 11:29, 2 October 2020
- entirely a matter of local administrative policy. This document does not require any specific administrative policy and does not propose27 KB (4,401 words) - 15:09, 5 October 2020
- recent work on DNS privacy solutions such as [DNS-over-TLS] is connection if the idle timeout set by local policy is exceeded.34 KB (4,924 words) - 14:05, 2 October 2020
- additional processes, such as policy-based enforcement of acceptable enterprise standards and policy.46 KB (6,486 words) - 11:28, 2 October 2020
- A server operator announces a default disclosure policy when the announced data collection policy with a 2308 error response code.68 KB (9,312 words) - 07:49, 4 October 2020
- only over secure connections. This overall policy is referred to as HTTP Strict Transport Security (HSTS). The policy is declared by web85 KB (12,480 words) - 18:53, 1 October 2020
- X.509 certificate's extensions of type "Policy OID" to a list of configured acceptable Policy OIDs for the roaming consortium. If one60 KB (8,293 words) - 10:33, 2 October 2020
- able to obtain the client's identity (perhaps due to privacy concerns the local security policy.169 KB (22,806 words) - 22:47, 11 October 2020
- Hosts may also generate or request IPv6 Privacy Addresses [PRIVv6]; there is support for DHCPv6 to assign privacy addresses to nodes in64 KB (9,075 words) - 17:59, 5 October 2020
- modify or redact this portion for privacy or legal reasons, it is of local policy and are thus outside the scope of this specification.38 KB (5,269 words) - 00:50, 22 October 2020
- particular policy (as reflected in the -- multiple next hops, policy routing, and Classless58 KB (6,221 words) - 18:42, 4 October 2020
- administrative exit selection policy of site S. As discussed in such as DHCPv6 can be used to disseminate an [[RFC3484]] policy table60 KB (9,192 words) - 15:35, 1 October 2020
- the requestor's local policy. Examples of actions the requestor Interface Specifications: DOCSIS 1.0 Baseline Privacy Interface39 KB (5,638 words) - 21:01, 5 October 2020
- Privacy concerns [Gont-DEEPSEC2011] [[RFC7721]] regarding IIDs embedding IEEE identifiers led to the introduction of "Privacy75 KB (9,979 words) - 12:59, 2 October 2020
- privacy lifetime, 20 years or more, it is important that the authentication, privacy, and one-way functions. These are ancillary103 KB (16,044 words) - 21:07, 19 October 2020
- filter according to their policy. policy rules, and those passing through end site firewalls can, in69 KB (10,214 words) - 18:46, 5 October 2020
- consent to the privacy implications of the policies in [6] is and act as policy decision points and trusted intermediaries along56 KB (8,406 words) - 05:20, 4 October 2020
- for it. Yet, others fear problems with regard to privacy when information. The policy to obtain these credentials allows ISPs/IAPs16 KB (2,139 words) - 11:58, 1 October 2020
- so that the state information can be used to implement policy (QoS) policies to the packets. This makes it a QOS Policy37 KB (5,458 words) - 15:30, 3 October 2020
- privacy concerns related to the use of MAC addresses in UUIDs. message (e.g., sending a BYE message to terminate a call for policy88 KB (11,781 words) - 08:18, 3 October 2020
- authorization policy. - It must be possible to protect the privacy of queries to the name14 KB (2,007 words) - 22:13, 3 October 2020
- normally port 2049.) This policy is no different with RDMA and privacy. This security mechanism will be unaffected by the RDMA71 KB (10,745 words) - 01:20, 12 October 2020
- policy. This periodicity or expiration policy should be address and port number, in accordance with a privacy protection58 KB (7,213 words) - 04:49, 22 October 2020
- client. Establishing policy rules in only one of these two firewalls Before sending PCP requests with possibly privacy-sensitive17 KB (2,304 words) - 13:17, 2 October 2020
- privacy, is provided. Accordingly, transport security in BEEP is privacy is in use, e.g.,63 KB (9,101 words) - 19:10, 3 October 2020
- validation policy and trust anchors used by the channel satisfy confidentiality protection and privacy protection is desired.42 KB (6,025 words) - 21:56, 5 October 2020
- local policy or via management interfaces. Remote LPI values are value might be modified by local policy relating to preferred paths106 KB (15,585 words) - 17:45, 1 October 2020
- A server operator announces a default disclosure policy when the announced data-collection policy with a 2308 error response code.66 KB (8,938 words) - 19:10, 13 October 2020
- A server operator announces a default disclosure policy when the announced data collection policy with a 2308 error response code.67 KB (9,148 words) - 19:34, 5 October 2020
- policy). Other registries may pare back the information as needed. "title" : "Beverage Policy",99 KB (11,915 words) - 08:33, 2 October 2020
- a normal, non-bulk registration (subject to SSP policy). If such a In order to provide support for privacy, the SSP SHOULD implement the67 KB (10,088 words) - 04:04, 22 October 2020
- privacy concerns around the clients informing the certificate issuer policy) with a bad_certificate_status_response(113) alert. This19 KB (2,685 words) - 22:16, 1 October 2020
- sender. The recipient can then use the ID as a lookup key for policy lookup policy. IKE mandates the use of the ID payload in Phase 1.84 KB (12,576 words) - 19:48, 5 October 2020
- been received by the notifier, but there is insufficient policy authorization policy. Clients SHOULD NOT attempt to re-subscribe.103 KB (14,727 words) - 16:20, 1 October 2020
- processes, and tools that maintain the privacy of the personally that privacy of customers' personally identifiable information (PII)63 KB (10,192 words) - 14:19, 1 October 2020
- policy is to print the job on a comparable medium. policy of the IPP Printer remotely.111 KB (12,795 words) - 01:02, 4 October 2020
- policy supports domain object validity periods, the validity period policy, this specification does not define actions to be taken upon77 KB (10,655 words) - 07:47, 4 October 2020
- 1174 - IAB Recommended Policy on Distributing Internet Identifier Assignment and IAB Recommended Policy Change to Internet53 KB (6,663 words) - 13:54, 16 October 2020
- handled, given a policy and a set of credentials. when security policy is distributed over a network or is otherwise69 KB (9,150 words) - 02:34, 20 October 2020
- policy-aware nodes that understand the POLICY_DATA element within provides security between policy-aware nodes. Policy-ignorant104 KB (14,559 words) - 17:29, 4 October 2020
- Req-13: SIP telephony devices SHOULD support the SIP Privacy header by populating headers with values that reflect the privacy71 KB (10,242 words) - 11:18, 5 October 2020
- via some protocol is often compared using some policy to make policy. For example, it might look up an access control list53 KB (7,820 words) - 21:56, 1 October 2020
- such as impersonation of MD's, privacy and confidentiality breaches, checking can also be used to counter replay attacks. Privacy and34 KB (4,894 words) - 11:31, 4 October 2020
- policy constraints they impose (e.g., charging for use). It SHOULD offer a confidentiality policy. All information exchanged in this28 KB (3,888 words) - 00:25, 4 October 2020
- 10. Security and Privacy Considerations Collecting Processes, can be sensitive for privacy reasons and need60 KB (7,497 words) - 23:20, 1 October 2020
- greater risks to the privacy of the users of networks under important tool for the protection of privacy within network95 KB (12,612 words) - 05:48, 22 October 2020
- safeguarded for privacy, and periodically purged within applicable === Security Policy ===78 KB (11,460 words) - 06:29, 2 October 2020
- authentication, authorization, and privacy models. Its intent is to service level agreements and privacy agreements when distributing or147 KB (17,031 words) - 11:41, 2 October 2020
- policy, and accounting functionality. It may also be collected and function, the BRAS is also an injection point for policy50 KB (7,926 words) - 20:04, 11 October 2020
- registrar in the home network may take local policy driven actions administrative domain, in order to retain the user's privacy.67 KB (9,815 words) - 02:26, 4 October 2020
- that privacy-conscious applications may well decide to perform [3] Alvestrand, H., "IETF Policy on Character Sets and Languages",18 KB (2,634 words) - 10:53, 5 October 2020
- server may use a local security policy to determine whether to client may need to make use of local policy information in making66 KB (9,466 words) - 11:28, 5 October 2020
- === Location Privacy === The Security Policy Database (SPD) entries in both the home agent and49 KB (8,001 words) - 17:30, 11 October 2020
- 1024 bits. Other TLS clients may, by policy, wish to use DHE only if policy, or it MAY decide to terminate the connection with a fatal51 KB (8,627 words) - 02:14, 3 October 2020
- Policy and Charging Control The Policy and Charging Control (PCC) framework is used for QoS72 KB (10,392 words) - 09:53, 22 October 2020
- privacy purposes). This optional information is needed to of this supporting information may be a processing policy, like a84 KB (11,794 words) - 08:53, 1 October 2020
- Depending on the authorization server's revocation policy, the and privacy since it reduces the likelihood for abuse of abandoned19 KB (2,736 words) - 23:14, 1 October 2020
- o It is easier to make policy decisions about whether or not to use policy decisions whether or not to use it.80 KB (11,483 words) - 08:05, 2 October 2020
- The COPS (Common Open Policy Service) Protocol policy control over QoS signaling protocols. The model does not make76 KB (10,497 words) - 03:24, 20 October 2020
- versions according to an explicit policy. than the ones their policy allows them to use. Policies may also143 KB (22,318 words) - 16:53, 5 October 2020
- towards the Internet), or this might be an explicit firewall policy possess prior knowledge of such default filtering policy, it SHOULD189 KB (29,838 words) - 20:45, 1 October 2020
- bandwidth, QOS, and policy based forwarding services. 4. Policy based forwarding on a dedicated L2 Virtual Circuit31 KB (4,572 words) - 15:59, 3 October 2020
- requesting host inserts the authorization information (e.g., a policy policy (e.g., they perform a resource reservation or change bindings69 KB (10,616 words) - 01:07, 22 October 2020
- policy supports domain object validity periods, the validity period policy, this specification does not define actions to be taken upon73 KB (10,307 words) - 19:32, 5 October 2020
- policy supports domain-object validity periods, the validity period policy, this specification does not define actions to be taken upon73 KB (10,194 words) - 19:09, 13 October 2020
- (A) an existing Unicode Policy, or An Explicit Precedent is a policy, procedure, encoding, algorithm, or23 KB (3,494 words) - 07:33, 4 October 2020
- detail the allocation policy and process for requesting new MT-ID o privacy32 KB (4,865 words) - 05:07, 2 October 2020
- the utility, such as dynamic pricing; according to local policy, the Privacy also becomes a serious issue in this case, as the sensed data54 KB (8,072 words) - 14:27, 1 October 2020
- The members of the Privacy and Security Research Group and the security label format supports a single security policy. If the32 KB (4,631 words) - 23:20, 16 October 2020
- anonymity and locational privacy. (policy) information governing the type of network service the97 KB (13,818 words) - 15:35, 11 October 2020
- owner while protecting the owner's privacy. The parameter registered using the "Specification Required" policy [IANA].22 KB (3,110 words) - 18:32, 11 October 2020
- user has to offer only a video stream. A user can use local policy sensitive. It is for this reason that privacy filtering plays a key75 KB (11,543 words) - 10:50, 5 October 2020
- policy (e.g., pre-positioned vs dynamic acquisition) and about where/ content by End Users in line with the CSP policy, or how to trust the63 KB (9,438 words) - 17:07, 1 October 2020
- * support for the Privacy Header be required * support for a specific privacy algorithm be required108 KB (16,677 words) - 09:02, 19 October 2020
- === Privacy Protection === be a privacy-impacting disclosure. Therefore gateways MAY support140 KB (19,675 words) - 01:22, 4 October 2020
- policy that describes the keys, and attributes such as an index 2. In addition to the policy associated with group keys, the group83 KB (11,664 words) - 13:56, 4 October 2020
- example Pretty Good Privacy (PGP) or Privacy Enhanced Mail (PEM) can policy or procedures, different possibilities are outlined to give73 KB (10,359 words) - 19:58, 19 October 2020
- private information. User consent to the privacy implications of the information and act as policy decision points and trusted67 KB (9,790 words) - 19:51, 11 October 2020
- Required" registration policy defined in [[RFC5226|RFC 5226]] [[RFC5226]]). | ENC | secu | Privacy Protected | a | o | 2228, 2773, 4217 |21 KB (2,427 words) - 16:05, 14 October 2020
- used to map classes of packets to specific policy actions; a policy table, docsDevFilterPolicyTable, which maps zero or95 KB (10,943 words) - 01:57, 20 October 2020
- - Neutral with respect to privacy: it reveals to servers no - Improving the protection of user privacy (although our74 KB (11,139 words) - 17:44, 19 October 2020
- <xcon:conference-floor-policy> </xcon:conference-floor-policy>217 KB (25,392 words) - 13:09, 1 October 2020
- may be withheld for privacy purposes. A thorough treatment of the privacy implications of describing66 KB (9,398 words) - 08:02, 2 October 2020
- export restrictions: separate authentication from privacy restrictions on export of privacy technology. Conversely, it112 KB (16,173 words) - 22:04, 29 September 2020
- o WEP - Wired Equivalent Privacy the link security mechanism, (e.g., when Wired Equivalent Privacy60 KB (8,796 words) - 18:12, 11 October 2020
- Sender and allowed by policy. message, per-sender, or programmed policy choice.69 KB (9,803 words) - 18:39, 11 October 2020
- 14.9. Consideration (5.1): Privacy The privacy policy of this protocol is explicit. In particular, the44 KB (6,558 words) - 02:30, 4 October 2020
- should use powerful encryption to provide security and privacy practical means to implement this policy.80 KB (11,715 words) - 01:30, 30 October 2020
- Certificate Policy and Certification Practices Framework authorities, policy authorities, and communities of interest that192 KB (22,109 words) - 06:13, 4 October 2020
- capability of binding a PW segment to a tunnel as a matter of policy PDUs away from their destination. In either case, the privacy of an53 KB (7,768 words) - 14:22, 11 October 2020
- PW must be processed or policy applied. It is therefore not label is a matter of local policy on the originating PE, but SHOULD85 KB (13,363 words) - 02:49, 22 October 2020
- external mechanisms such as mobility management, policy, location privacy requirement and so on. Further, the same QoS mechanism19 KB (2,862 words) - 04:57, 4 October 2020
- (see below), and one or more IPv6 privacy addresses [[RFC4941]]. prefix is desirable for addressing consistency and policy107 KB (16,055 words) - 06:15, 2 October 2020
- ICANN's Uniform Dispute Resolution Policy (URDP) for the purposes of attributes: the party who sets the blocking policy, the purpose of72 KB (10,628 words) - 13:51, 2 October 2020
- policy which is attached to the zone. One should start looking for === Application of local policy ===34 KB (5,316 words) - 08:25, 4 October 2020
- what routes to accept is always considered a local policy matter. - With personal information, privacy issues19 KB (2,799 words) - 22:32, 3 October 2020
- the local policy of the ISP. Such policy may vary substantially explained in more detail in Figure 1. Depending on local policy and43 KB (5,198 words) - 07:02, 2 October 2020
- privacy reasons, it might decide to perform overload control only for request received on an untrusted link can leak privacy in the form of76 KB (11,437 words) - 05:42, 2 October 2020
- where a privacy Network user has multiple sessions on the NAS, or if the privacy NAI is67 KB (8,744 words) - 12:55, 11 October 2020
- privacy addresses [[RFC1918]], etc.) are self-generated by [[RFC3972]], IPv6 Privacy Addresses [[RFC4941]], StateLess Address75 KB (10,967 words) - 20:57, 11 October 2020
- RPSL Routing Policy System Replication 2769* RSVP Signaled Preemption Priority Policy Element 2751*78 KB (7,393 words) - 00:39, 20 October 2020
- o Authentication and Privacy Capabilities Provider Selection (based on policy, performance, cost, etc.)50 KB (7,579 words) - 08:14, 19 October 2020
- to the user, the UAS SHOULD handle the message based on local policy. This policy could mean: the message is deleted undisplayed,35 KB (4,941 words) - 01:55, 4 October 2020
- DNS Security (DNSSEC) [2], Pretty Good Privacy (PGP), or X.509 to does require per-HIT-pair SAs (and SPIs), and a decrease of policy52 KB (7,687 words) - 21:13, 4 October 2020
- New cached info types can be added following the policy described in policy allows the use of this extension).29 KB (3,540 words) - 02:40, 3 October 2020
- can contact it (subject to the NAT's security policy). The security policy of a NAT is independent of its mapping behavior43 KB (6,365 words) - 17:32, 11 October 2020
- configuration policy. Furthermore, a Subordinate Printer object MAY, implementation and/or configuration policy.90 KB (11,522 words) - 13:02, 4 October 2020