Hello Anita,
queue-list are part of configuration of legacy queueing :
Custom Queueing
these are currently superseaded by LLQ CBWFQ provided by MGC.
there can be application niches for their capability to treat legacy non IP protocols including IPX, AT and others but in a IP only scenario there shouldn't be reasons to use them anymore.
see
RT-TO-CRN-POPE-1(config)#queue-list 1 protocol ?
aarp AppleTalk ARP
appletalk AppleTalk
arp IP ARP
bridge Bridging
bstun Block Serial Tunnel
cdp Cisco Discovery Protocol
compressedtcp Compressed TCP
decnet DECnet
decnet_node DECnet Node
decnet_router-l1 DECnet Router L1
decnet_router-l2 DECnet Router L2
dlsw Data Link Switching
ip IP
ipx Novell IPX
llc2 llc2
pad PAD links
qllc qllc protocol
rsrb Remote Source-Route Bridging
snapshot Snapshot routing support
stun Serial Tunnel
RT-TO-CRN-POPE-1(config)#queue-list 1 protocol
RT-TO-CRN-POPE-1(config)#queue-list 1 ?
default Set custom queue for unspecified datagrams
interface Establish priorities for packets from a named interface
lowest-custom Set lowest number of queue to be treated as custom
protocol priority queueing by protocol
queue Configure parameters for a particular queue
stun Establish priorities for stun packets
if you like look for Custom Queueing Configuration in CCO
Custom Queueing in comparison to CBWFQ lacks elasticity the configured queues are served in round robin taking up to a preconfigured amount of bytes from each queue.
If a queue is empty is processed but doesn't free resources for other traffic types.
Instead this happens in CBWFQ.
Hope to help
Giuseppe
