]> Huawei

101 Software Avenue, Yuhua District Jiangsu 210012 China maqiufang1@huawei.com

Huawei

101 Software Avenue, Yuhua District Jiangsu 210012 China bill.wu@huawei.com

Orange

Rennes 35000 France mohamed.boucadair@orange.com

Old Dog Consulting

United Kingdom daniel@olddog.co.uk

Operations and Management OPSAWG ACL Policy-based BYOD Access control This document defines a YANG module for policy-based network access control, which provides consistent and efficient enforcement of network access control policies based on group identity. In addition, this document defines a mechanism to ease the maintenance of the mapping between a user-group ID and a set of IP/MAC addresses to enforce policy-based network access control. Also, the document defines a common schedule YANG module which is designed to be applicable for policy activation based on date and time conditions. In addition, the document defines a RADIUS attribute that is used to communicate the user group identifier as part of identification and authorization information.

Introduction With the increased adoption of remote access technologies (e.g., Virtual Private Networks (VPNs)) and Bring Your Own Device (BYOD) policies, enterprises adopted more flexibility related to how, where, and when employees work and collaborate. However, more flexibility comes with increased risks. Enabling office flexibility (e.g., mobility across many access locations) for large-scale employees induces a set of challenges compared to conventional network access management approaches. Examples of such challenges are listed below: Endpoints do not have a stable IP address. For example, Wireless LAN (WLAN) and VPN clients, as well as back-end Virtual Machine (VM)-based servers, can move; their IP addresses could change as a result. This means that relying on IP/transport fields (e.g., the 5-tuple) is inadequate to ensure consistent and efficient security policy enforcement. IP address-based policies may not be flexible enough to accommodate endpoints with volatile IP addresses. With the massive adoption of teleworking, there is now a need to apply different security policies to the same set of users under different circumstances (e.g., prevent relaying attacks against a local attachment point to the Enterprise network). For example, network access might be granted based upon criteria such as users' access location, source network reputation, users' role, time-of- day, type of network device used (e.g., corporate issued device versus personal device), device's security posture, etc. This means the network needs to recognize the users' identity and their current context, and map the users to their correct access entitlement to the network. This document defines a common schedule YANG module which is designed to be applicable for policy activation based on date and time condition. This model can be used in other scheduling contexts. The document also defines a YANG module for policy-based Network Access Control (), which extends the IETF Access Control Lists (ACLs) module defined in . This module defined in is meant to ensure consistent enforcement of ACL policies based on group identity. In addition, this document defines a mechanism to establish a mapping between the user-group ID and common IP packet headers and other enclosed packet data (e.g., MAC address) to execute the policy-based access control. Last, the document defines a RADIUS attribute that is used to communicate the user group identifier as part of identification and authorization information (). As the ACL notion has been generalized, not to be device-specific, but also be defined at network/administrative domain levels , the YANG module for policy-based network access control defined in this document does not limit how it can be used.

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. The meanings of the symbols in tree diagrams are defined in . The document uses the terms defined in . In the current version of the draft, the term "endpoint" refers also to a host device or end user that actually connect to a network. While host device here refers to servers, IoTs and other devices owned by the enterprise.

Sample Usage Access to some networks (e.g., Enterprise Networks) require to recognize the users' identities no matter how, where, and when they connect to the network resources. Then, the network maps the (conencting) users to their access authorization rights. Such rights are defined following local policies. As discussed in the introduction, because there is a large number of users and the source IP addresses of the same user are in different network segments, deploying a network access control policy for each IP address or network segment is heavy workload. An alternative approach is to configure endpoint groups to classify users and enterprise devices and associate ACLs with endpoint groups so that endpoint in each group can share a group of ACL rules. This approach greatly reduces the workload of the administrators and optimizes the ACL resources. The Network ACLs (NACLs) can be provisioned on devices using specific mechanisms, such as or . Network access control policies may need to vary over time. For example, companies may restrict/grant employees access to specific resources (internal and/or external resources) during work hours, while another policy is adopted during off-hours and weekends. A network administrator may also require to enforce traffic shaping (Section 2.3.3.3 of ) and policing (Section 2.3.3.4 of ) during peak hours in order not to affect other data services.

Policy-based Network Access Control

Overview To provide real-time and consistent enforcement of access control policies, the following functional entities and interfaces are involved: A Service Orchestrator which coordinates the overall service, including security policies. The service may be connectivity or any other resources that can be hosted and offerd by a newtork. The SDN Controller is responsible for maintaining endpoint-group based ACLs and mapping the endpoint-group to the associated attributes information (e.g., IP/MAC address). The SDN Controller also works as the Policy Decision Point (PDP) and pushes the required access control policies to relevant PEPs (Policy Enforcement Points) that need them. A PDP is also known as "policy server" . The SDN Controller may interact with AAA server or NAS. A Network Access Server (NAS) entity which handles authentication requests. The NAS interacts with an AAA server to complete user authentication using Remote Authentication Dial-in User Service (RADIUS) . When access is granted, the AAA server provides the group identifier (group ID) to which the user belongs when the user first logs onto the network. A new attribute is defined in . The Policy Enforcement Point (PEP) is the central entity which is responsible for enforcing appropriate access control policies. In some cases, A PEP may map incoming packets to their associated source or destination endpoint-group IDs, and acts on the endpoint-group ID based ACL policies, e.g., a NAS as the PEP or a group identifier could be carried in packet header (see Section 6.2.3 in ). While in other cases, the SDN controller maps group ID to the related common packet header and delivers IP/MAC address based ACL policies to the required PEPs. Multiple PEPs can be involved in a network. A PEP exposes a NETCONF interface to the SDN Controller . provides the overall architecture and procedure for policy- based access control management.

In reference to , the following typical flow is experienced: Step 1: Administrators (or the Orchestrator) configure an SDN controller with network-level ACLs using the YANG module defined in . Step 2: When a user first logs onto the network, the user is required to be authenticated (e.g., using user name and password) at the NAS. Step 3: The authentication request is then relayed to the AAA server using RADIUS . It is assumed that the AAA server has been appropriately configured to store user credentials, e.g., user name, password, group information and other user attributes. If the authentication request succeeds, the user is placed in a user-group which is returned to the network access server as the authentication result (see ). If the authentication fails, the user is not assigned a user- group, which also means that the user has no or limited access permissions for the network (as a fucntion of the local policy). ACLs are enforced so that flows from that IP address are discarded (or rate-limited) by the network. In some implementations, AAA server can be integrated with an SDN controller. Step 4: Either the AAA server or the NAS notify the SDN controller the mapping between the user-group ID and related common packet header attributes (e.g., IP/MAC address). Step 5: Either group or IP/MAC address based access control policies are maintained on relevant PEPs under the controller's management.

Endpoint Group

User Group The user-group ID is an identifier that represents the collective identity of a group of users. It is determined by a set of predefined policy criteria (e.g., source IP address, geolocation data, time of day, or device certificate). Users may be moved to different user-groups if their composite attributes, environment, and/or local enterprise policy change. A user is authenticated, and classified at the AAA server, and assigned to a user-group. A user's group membership may change as aspects of the user change. For example, if the user-group membership is determined solely by the source IP address, then a given user's user-group ID will change when the user moves to a new IP address that falls outside of the range of addresses of the previous user-group. This document does not make any assumption about how user groups are defined. Such considerations are deployment specific and are out of scope. However, and for illustration purposes, shows an example of how user-group definitions may be characterized. User- groups may share several common criteria. That is, user-group criteria are not mutually exclusive. For example, the policy criteria of user-groups R&D Regular and R&D BYOD may share the same set of users that belong to the R&D organization, and differ only in the type of clients (firm-issued clients vs. users' personal clients). Likewise, the same user may be assigned to different user- groups depending on the time of day or the type of day (e.g., weekdays versus weekends), etc. Group Name Group ID Group Role R&D 10 R&D employees R&D BYOD 11 Personal devices of R&D employees Sales 20 Sales employees VIP 30 VIP employees

Device Group The device-group ID is an identifier that represents the collective identity of a group of enterprise end devices. An enterprise device could be an server that hosts applications or software that deliver services to enterprise users. It could also be an enterprise IoT device that serve a limited purpose, e.g., a printer that allows users to scan, print and send emails. shows an example of how device-group definitions may be characterized. Group Name Group ID Group Type Workflow 40 Workflow resource servers R&D Resource 50 R&D resource servers Sales Resource 54 Sales resource servers Users accessing to enterprise device should be strictly controlled. Matching abstract device group ID instead of specified addresses in ACL polices helps shield the consequences of address change (e.g., back-end Virtual Machine (VM)-based server migration).

YANG Modules

The Schedule YANG Module This module defines a common schedule YANG module. It is inspired from the "period of time" and "recurrence rule" format defined in . This module is defined as a standalone module rather than in the UCL module with the intention that the time/date definition can be reused.

Module Overview provides an overview of the tree structure of the "ietf- schedule" module.

The YANG Module This module imports types defined in .

file="ietf-schedule@2023-01-19.yang" module ietf-schedule { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-schedule"; prefix schedule; import ietf-yang-types { prefix yang; revision-date 2023-01-23; reference "RFC XXXX: Common YANG Data Types"; } organization "IETF OPSAWG Working Group"; contact "WG Web: WG List: "; description "This YANG module defines two properties of an iSchedule object:period of time and recurrence rule. Copyright (c) 2023 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; revision 2023-01-19 { description "Initial revision."; reference "RFC XXXX: A Policy-based Network Access Control"; } typedef weekday { type enumeration { enum sunday { description "Sunday of the week."; } enum monday { description "Monday of the week."; } enum tuesday { description "Tuesday of the week."; } enum wednesday { description "Wednesday of the week."; } enum thursday { description "Thursday of the week."; } enum friday { description "Friday of the week."; } enum saturday { description "Saturday of the week."; } } description "Seven days of the week."; } grouping period { description "This grouping is defined for period of time property."; container period-of-time { description "This container is defined to identify period values that contain a precise period of time."; choice forms { description "Two forms of period of time."; case period-explicit { description "A period of time is identified by its start and its end."; leaf explicit-start { type yang:date-and-time; description "Period start time."; } leaf explicit-end { type yang:date-and-time; description "Period end time."; } } case period-start { description "A period of time is defined by a start and a positive duration of time."; leaf start { type yang:date-and-time; description "Period start time."; } leaf duration { type yang:time-no-zone; description "Duration of the time."; } } } } } grouping recurrence { description "This grouping is defined to identify properties that contain a recurrence rule specification"; container recurrence { description "Recurrence rule definition."; leaf freq { type enumeration { enum secondly { value 1; description "Repeating events based on an interval of a second or more."; } enum minutely { value 2; description "Repeating events based on an interval of a minute or more."; } enum hourly { value 3; description "Repeating events based on an interval of an hour or more."; } enum daily { value 4; description "Repeating events based on an interval of a day or more."; } enum weekly { value 5; description "Repeating events based on an interval of a week or more."; } enum monthly { value 6; description "Repeating events based on an interval of a month or more."; } enum yearly { value 7; description "Repeating events based on an interval of a year or more."; } } mandatory true; description "This parameter is defined to identify the type of recurrence rule."; } choice until-or-count { description "Modes to bound the recurrence rule."; case until { description "This case defines a way that bounds the recurrence rule in a inclusive manner."; leaf until { type union { type yang:date-no-zone; type yang:date-and-time; } description "This parameter specifies a date-no-zone or date-time value to bounds the recurrence."; } } case count { description "This case defines the number of occurrences at which to range-bound the recurrence."; leaf count { type uint32; description "The positive number of occurrences at which to range-bound the recurrence."; } } } leaf interval { type uint32; default "1"; description "A positive integer representing at which intervals the recurrence rule repeats."; } leaf-list bysecond { type uint32 { range "0..60"; } description "A list of seconds within a minute."; } leaf-list byminute { type uint32 { range "0..59"; } description "A list of minutes within an hour."; } leaf-list byhour { type uint32 { range "0..23"; } description "Specify a list of hours of the day."; } list byday { key "weekday"; description "Specify a list of days of the week."; leaf direction { when '(enum-value(../../freq) >= 6) and ' + '(enum-value(../../freq) = 7) and not(../../byyearweek)'; type int32 { range "-53..-1|1..53"; } description "When specified, it indicates the nth occurrence of a specific day within the MONTHLY or YEARLY 'RRULE'."; } leaf weekday { type schedule:weekday; description "Corresponding to seven days of the week."; } } leaf-list bymonthday { type int32 { range "-31..-1|1..31"; } description "Specifies a list of days of the month."; } leaf-list byyearday { type int32 { range "-366..-1|1..366"; } description "Specifies a list of days of the year."; } leaf-list byyearweek { when 'enum-value(../freq)=7'; type int32 { range "-53..-1|1..53"; } description "Specifies a list of weeks of the year."; } leaf-list byyearmonth { type uint32 { range "1..12"; } description "Specifies a list of months of the year."; } leaf-list bysetpos { type int32 { range "-366..-1|1..366"; } description "Specifies a list of values that corresponds to the nth occurrence within the set of recurrence instances specified by the rule."; } leaf-list wkst { type schedule:weekday; default "monday"; description "Specifies the day on which the workweek starts."; } } } } ]]>

The UCL Extension to the ACL Model

Module Overview provides the tree strcuture of the "ietf-ucl-acl" module.

This module specifies an extension to the IETF ACL model such that the UCL group index can be referenced by augmenting the "match" data node.

The YANG Module This module imports types defined in , , and .

file="ietf-ucl-acl@2023-01-19.yang" module ietf-ucl-acl { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ucl-acl"; prefix uacl; import ietf-access-control-list { prefix acl; reference "RFC 8519: YANG Data Model for Network Access Control Lists (ACLs)"; } import ietf-schedule { prefix schedule; reference "RFC XXXX: A Policy-based Network Access Control"; } organization "IETF OPSWG Working Group"; contact "WG Web: WG List: "; description "This YANG module defines XXX. Copyright (c) 2023 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; revision 2023-01-19 { description "Initial revision."; reference "RFC XXXX: A Policy-based Network Access Control"; } feature match-on-endpoint-group { description "The device can support matching on endpoint groups."; } feature match-on-time { description "The device can support a time-based condition match."; } augment "/acl:acls/acl:acl" { description "add a new container to store endpoint group information."; container endpoint-groups { description "Container definition for the endpoint group."; list endpoint-group { key "endpoint-group-id"; description "Definition of the endpoint group list."; leaf endpoint-group-id { type uint32 { range "0..4294967294"; } description "The endpoint group ID that uniquely identifies an endpoint group."; } choice group-type { description "Choice of each different type of endpoint."; case user-group { description "The employee that actually connects to the network."; container user-group { description "Defines the user-group container."; leaf role { type string; description "The common role of this user-group."; } } } case device-group { description "The static resources in a network, such as a specific application."; container device-group { description "Defines the device-group container."; leaf device-type { type string; description "The type of the static resource."; } } } } } } } augment "/acl:acls/acl:acl/acl:aces/acl:ace/acl:matches" { description "Add another choice to allow ace match based on endpoint group id."; container endpoint-group { if-feature "match-on-endpoint-group"; description "Add new match types."; container source-match { description "The source matched information."; leaf endpoint-group-id { type leafref { path "../../../../../../endpoint-groups/endpoint-group/"+ "endpoint-group-id"; } description "The matched source endpoint group ID."; } } container destination-match { description "The destination matched information."; leaf endpoint-group-id { type leafref { path "../../../../../../endpoint-groups/endpoint-group/"+ "endpoint-group-id"; } description "The matched destination endpoint group ID."; } } } } augment "/acl:acls/acl:acl/acl:aces/acl:ace" { if-feature "match-on-time"; description "Add a new parameter to the Access Control Entry (ACE)."; container time-range { description "This container defines when the access control entry rules are in effect. If it is not configured, the access control entry is immediately and always in effect."; choice time-range-type { description "Choice based on the type of the time range."; case periodic-range { description "A periodic range of time to take effect."; uses schedule:recurrence; } case absolute-range { description "A single precise period of time to take effect."; uses schedule:period; } } } } } ]]>

User Access Control Group ID RADIUS Attribute The User-Access-Group-ID RADIUS attribute and its embedded TLVs are defined with globally unique names. The definition of the attribute follows the guidelines in Section 2.7.1 of . This attribute is used to indicate the user-group ID to be used by the NAS. When the User-Access-Group-ID RADIUS attribute is present in the RADIUS Access-Accept, the system applies the related access control to the users after it authenticates. The value fields of the Attribute are encoded in clear and not encrypted as, for example, Tunnel- Password Attribute . The User-Access-Group-ID Attribute is of type "string" as defined in Section 3.5 of . The User-Access-Group-ID Attribute MAY appear in a RADIUS Access- Accept packet. It MAY also appear in a RADIUS Access-Request packet as a hint to the RADIUS server to indicate a preference. However, the server is not required to honor such a preference. The User-Access-Group-ID Attribute MAY appear in a RADIUS CoA-Request packet. The User-Access-Group-ID Attribute MAY appear in a RADIUS Accounting- Request packet. The User-Access-Group-ID Attribute MUST NOT appear in any other RADIUS packet. The User-Access-Group-ID Attribute is structured as follows:

The User-Access-Group-ID Attribute is associated with the following identifier: 241.TBA1.

RADIUS Attributes The following table provides a guide as what type of RADIUS packets that may contain User-Access-Group-ID Attribute, and in what quantity.

Security Considerations

YANG The YANG modules specified in this document defines schema for data that is designed to be accessed via network management protocols such as NETCONF or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS . The Network Configuration Access Control Model (NACM) provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. The "ietf-schedule" module defines a set of types and groupings. These nodes are intended to be reused by other YANG modules. The module by itself does not expose any data nodes that are writable, data nodes that contain read-only state, or RPCs. As such, there are no additional security issues related to the "ietf- schedule" module that need to be considered. There are a number of data nodes defined in the "ietf-ucl-acl" YANG module that are writable, creatable, and deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations to these data nodes could have a negative effect on network and security operations. TBC TBC

* ]]>

RADIUS RADIUS-related security considerations are discussed in . This document targets deployments where a trusted relationship is in place between the RADIUS client and server with communication optionally secured by IPsec or Transport Layer Security (TLS) .

IANA Considerations

YANG This document registers the following URIs in the "IETF XML Registry" .

This document registers the following YANG modules in the "YANG Module Names" registry .

RADIUS This document requests IANA to assign a new RADIUS attribute types from the IANA registry "Radius Attribute Types" : Value Description Data Type Reference 241.TBA1 User-Access-Group-ID string This-Document

This document defines a data model for Access Control Lists (ACLs). An ACL is a user-ordered set of rules used to configure the forwarding behavior in a device. Each rule is used to find a match on a packet and define actions that will be performed on the packet. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK] The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] Constructor University This document defines a collection of common data types to be used with the YANG data modeling language. This version of the document adds several new type definitions and obsoletes RFC 6991. This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. This document defines a data model for Large-Scale Measurement Platforms (LMAPs). The data model is defined using the YANG data modeling language. The Remote Authentication Dial-In User Service (RADIUS) protocol is nearing exhaustion of its current 8-bit Attribute Type space. In addition, experience shows a growing need for complex grouping, along with attributes that can carry more than 253 octets of data. This document defines changes to RADIUS that address all of the above problems. RADIUS specifications have used data types for two decades without defining them as managed entities. During this time, RADIUS implementations have named the data types and have used them in attribute definitions. This document updates the specifications to better follow established practice. We do this by naming the data types defined in RFC 6158, which have been used since at least the publication of RFC 2865. We provide an IANA registry for the data types and update the "RADIUS Attribute Types" registry to include a Data Type field for each attribute. Finally, we recommend that authors of RADIUS specifications use these types in preference to existing practice. This document updates RFCs 2865, 3162, 4072, 6158, 6572, and 7268. This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.This document obsoletes RFC 6536. This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK] IANA Telefonica Telefonica Orange RFC 8519 defines a YANG data model for Access Control Lists (ACLs). This document discusses a set of extensions that fix many of the limitations of the ACL model as initially defined in RFC 8519. Discussion Venues This note is to be removed before publishing as an RFC. Discussion of this document takes place on the Network Modeling Working Group mailing list (netmod@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/netmod/. Source for this draft and an issue tracker can be found at https://github.com/oscargdd/draft-dbb-netmod-enhanced-acl. This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language. This document defines an architecture for implementing scalable service differentiation in the Internet. This memo provides information for the Internet community. This document is a glossary of policy-related terms. It provides abbreviations, explanations, and recommendations for use of these terms. The intent is to improve the comprehensibility and consistency of writing that deals with network policy, particularly Internet Standards documents (ISDs). This memo provides information for the Internet community. This document is concerned with specifying a framework for providing policy-based control over admission control decisions. This memo provides information for the Internet community. Ciena Corporation Futurewei Technologies The IETF Network Virtualization Overlays (NVO3) Working Group Chairs and Routing Area Director chartered a design team to take forward the encapsulation discussion and see if there was potential to design a common encapsulation that addresses the various technical concerns. This document provides a record, for the benefit of the IETF community, of the considerations arrived at by the NVO3 encapsulation design team, which may be helpful with future deliberations by working groups over the choice of encapsulation formats. There are implications of having different encapsulations in real environments consisting of both software and hardware implementations and within and spanning multiple data centers. For example, OAM functions such as path MTU discovery become challenging with multiple encapsulations along the data path. The design team recommended Geneve with a few modifications as the common encapsulation. This document provides more details, particularly in Section 7. This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol. [STANDARDS-TRACK] This document defines a set of RADIUS (Remote Authentication Dial In User Service) attributes designed to support the provision of compulsory tunneling in dial-up networks. This memo provides information for the Internet community. This document specifies a transport profile for RADIUS using Transport Layer Security (TLS) over TCP as the transport protocol. This enables dynamic trust relationships between RADIUS servers. [STANDARDS-TRACK] Huawei Goldman Sachs France Telecom France Telecom Huawei Huawei F5 Networks This draft defines the User-group Aware Policy Control (UAPC) framework, which facilitates consistent enforcement of security policies based on user group identity. Policies are used to control security policy enforcement using a policy server and a security controller. Northbound APIs are also discussed. Huawei Technologies Huawei Technologies Huawei Technologies This document defines the autonomic technical Objectives for IP address/prefix to access control group IDs mapping information. The Objectives defined can be used in Generic Autonomic Signaling Protocol (GRASP) to make the policy enforcement point receive IP address and its tied access control groups information directly from the access authentication points and facilitate the group based policy enforcement.

Changes between Revisions v00 - v01 * Define a common schedule yang module and reuse in UCL yang module to support time/date-based activation condition. Either group-based or address-based ACL policies could be enforced at PEP, and allow group-based ACL policies maintained at the network controller. Optimize the process in section 4.1. Extend ACL module to support a generalized endpoint-group to cover both end users (e.g., enterprise employees) and enterprise hosts (e.g., IoT devices or servers); Simplify the definition of group in UCL model with only the most necessary group ID retained.

Acknowledgments This work has benefited from the discussions of User-group-based Security Policy over the years. In particular, and provide mechanisms to establish the mapping between the IP address/prefix of user and access control group ID. Jianjie You, Myo Zarny, Christian Jacquenet, Mohamed Boucadair, and Yizhou Li contributed to an earlier version of . We would like to thank the authors of that draft on modern network access control mechanisms for material that assisted in thinking about this document. The authors would like to thank Joe Clarke, Bill Fenner, Benoit Claise, Rob Wiltion, David Somers-Harris for their valuable comments and great input to this work.